On Wed, 2002-10-02 at 16:03, [EMAIL PROTECTED] wrote: > +1 +1 for me too
> > IMHO, Zope releases should, in this scenario, be configured by default to > use a custom_zodb.py file with ClientStorage over a socket at startup, > making the default config of Zope one that uses ZEO. I'm not sure about this. Beside Toby's comment about the problems of using TCP and UNIX sockets, using ZEO decreases performance in the single client scenario. I do believe it should be as easy as possible to use ZEO in Zope (and so I support the inclusion of ZEO in Zope by default) but this should be a conscious decision, made by someone that's aware of the consequences (such as increased read and write conflict errors). > Also, start scripts > should be distributed with options to support both the following: > - Zope's start script Start ZEO via ZEO's start.py, > wait for confirmation of loaded storages, > then start Zope's z2.py > - Separate shell scripts to start each That would certainly be nice. It's not necessary, however, to wait for the ZEO server to start before starting the ZEO client, as it will continuously try to connect to the server. > [...] Cheers, Leo -- Ideas don't stay in some minds very long because they don't like solitary confinement. _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
