> > And you're revamping an awful lot of CP internals at the moment to > > finish the 64-bit enablement. It's worth bringing up the idea at least. > > By all means. But even in a 64-bit world, much of CP (including the ACI) > runs in a 31-bit execution space with the flexiblity to map any page into > that 31-bit space. The parts of CP that manage the 31-bit space are, of > course, 64-bit, as are those that need to access possibly more than 2GB of > data are also 64-bit enabled.
I was under the impression that that mapping approach was a temporary rest stop on the evolution, though. If there is still major restructuring to be done, then it'd be worth looking into some of the other general interface stuff (cf how SPXTAPE works, etc) at that point, or at least start poking at the concept. Using a "service access point" model would keep the services available for CMS but also make them easier to access in a pure hosting model. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
