Another idea that comes to mind is a sort of compatibility
package, which would offer older packages (for ACS 3.4.x and
OACS 3.x) a very close approximation to the API they use. They
could be different, but just close enough that porting to the
compatibility package would be less effort than porting the entire
thing over outright. Is this at all feasible? I don't know the OACS
4.5 toolkit enough to know.
So for example, they would provide wrappers to the
authentication routines, and so on. Maybe they could be called
the backwards compatibility API, or something like that..
