From thread: RE: [Zope] Large Portal requirements (was: Other web servers?) At 03:15 PM 6/14/99 -0400, Michel wrote: In the future, we will be have the client server model of ZODB3 (which will be a commercial product) that lets you have multiple Zope frontend processes (possibly on different machines) accessing multiple database backend processes (possibly on different machines). Also, ZServer is currently multi-threaded, but there is no theoretical limitation to making it multi-process, in which each Zope instance will have it's own Python and thus it's own global Python lock, thus giving the OS the ability to schedule multiple processes among multiple processors, a little heavier than threads on multi-processor, but *vastly* easier to impliment and far more stable.

And then...

From thread: RE: [Zope] How stable is the 2.0 alpha release? At 11:12 AM 6/16/99 -0400, Michel wrote: Yes, 2.0 alpha will work fine with an existing Database *if* you run it in ZODB2 mode (no concurrency). If you run it in ZODB3 mode (the default) your Data.bbb file will not even be used, rather, a different file called Data.fs (fs = File Storage, remember, ZODB3 can use multiple backend stores) will be used. Data.fs and Data.bbb are two different formats, and are incompatable. Real Soon Now we will have a conversion script to upgrade from Data.bbb format to Data.fs format, but I for one, will promise no date.

To clarify my understanding. Will their be a non client-server version of ZODB3 which offers concurrency that will be a part of the non-commercial, open source part of Zope? Jimmie Houchin