current best of breed ZEO for Zope 2.6.2 in production?
Hi, I'm with a client in the process of setting up a production environment with ZEO. Which of the ZEOs should I use? * Old (t)rusty ZEO 1.0? * ZEO 2.0? * any one of the ZEO releases at http://www.zope.org/Products/ZEO ? * a ZEO ripped off of a ZODB release? Which one? (maybe even this last RC?) * In this case, should I make the ZEO server out of this ZODB release or should I just combine the ZEO server part into Zope and serve ZEO out of that? * If use a standalone ZODB release as ZEOServer, can/should I run it on Python2.2 While using Python2.1 ZEOClients? (I'm not running Zope 2.6.2 on Python 2.2) Cheers, Leo
On Thu, 2003-10-02 at 11:02, Leonardo Rochael Almeida wrote:
I'm with a client in the process of setting up a production environment with ZEO.
Which of the ZEOs should I use?
* Old (t)rusty ZEO 1.0?
No. Lots of known bugs, no support available.
* ZEO 2.0? * any one of the ZEO releases at http://www.zope.org/Products/ZEO ?
All of the releases on this page, including 2.0, are obsolete. It says so at the top of the page.
* a ZEO ripped off of a ZODB release? Which one? (maybe even this last RC?)
That is your best bet, although ripped off suggests that you have to do something special. In fact, ZEO is only released as part of ZODB3 these days. It will also be included directly in Zope 2.7. The last release candidate should work, although you will need to upgrade the ZODB code in the Zope clients as well as in the server. A server running ZODB 3.2 can talk interoperate with ZODB 3.1 clients, but I assume you don't have any version of ZEO installed on the clients.
* In this case, should I make the ZEO server out of this ZODB release or should I just combine the ZEO server part into Zope and serve ZEO out of that?
I would just use ZODB3 for the server. Running ZEO from a Zope software home can cause problems, because Zope code can get loaded during conflict resolution and imports of Zope have a lot of side effects.
* If use a standalone ZODB release as ZEOServer, can/should I run it on Python2.2 While using Python2.1 ZEOClients? (I'm not running Zope 2.6.2 on Python 2.2)
I don't think Zope Corp. has an official position on this. Personally, I think you'd be best off using Python 2.3.2 or Python 2.2.3 if you can't use 2.3. Jeremy
* ZEO 2.0? * any one of the ZEO releases at http://www.zope.org/Products/ZEO ?
All of the releases on this page, including 2.0, are obsolete. It says so at the top of the page.
I thought that was easy to miss, so I changed the heading from Zope Enterprise Objects to Zope Enterprise Objects (OBSOLETE) It could probably use more text explaining what to do instead. I'd do that if I thought I knew <wink>.
Tim Peters writes:
* ZEO 2.0? * any one of the ZEO releases at http://www.zope.org/Products/ZEO ?
All of the releases on this page, including 2.0, are obsolete. It says so at the top of the page.
I thought that was easy to miss, so I changed the heading from
Zope Enterprise Objects
to
Zope Enterprise Objects (OBSOLETE)
And I still missed it! Amazing! it must've been the pre-lunch hunger or something... Maybe you should use a blink tag and a red font tag inside a one cell table with a thick border (/me runs from the HTML-standards mob).
It could probably use more text explaining what to do instead. I'd do that if I thought I knew <wink>.
Yes, that's exactly what I'm looking for: what is the current "blessed" procedure for using ZEO with Zope? The client will be using the binary Zope 2.6.2 package, BTW. I've (finally) read the ZODB page and it says Zope 2.6.2 doen't need a ZODB surgery to use ZEO. This is good since I don't want to scare the client with weird surgeries for a Production installation :-) (I'm mentoring them on the installation, not installing it for them). Since we'll be using python-2.1.3, ZODB 3.2 isn't an option. Does ZODB 3.1.4 (the last ZODB release according to the ZODB3.1 page) fix the "one client changes an object but the others don't see the change" bug reported here recently? If yes, should I just copy over the ZEO package or do you guys still recomend that I replace all of Zope262 ZODB with the standalone one? Cheers, Leo
On Thu, Oct 02, 2003 at 02:34:58PM -0300, Leonardo Rochael Almeida wrote:
Since we'll be using python-2.1.3, ZODB 3.2 isn't an option. Does ZODB 3.1.4 (the last ZODB release according to the ZODB3.1 page) fix the "one client changes an object but the others don't see the change" bug reported here recently?
I haven't seen that bug since I installed ZEO from 3.1.2. Presumably it's still fixed in 3.1.4 :-) -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's SUPER PELICAN MEGA! (random hero from isometric.spaceninja.com)
On Thu, 2003-10-02 at 13:34, Leonardo Rochael Almeida wrote:
I thought that was easy to miss, so I changed the heading from
Zope Enterprise Objects
to
Zope Enterprise Objects (OBSOLETE)
And I still missed it! Amazing! it must've been the pre-lunch hunger or something... Maybe you should use a blink tag and a red font tag inside a one cell table with a thick border (/me runs from the HTML-standards mob).
Maybe we should just delete it. On the other hand, Jim asked me today how someone would navigate from the zope.org home page to the current ZODB release. I don't have any idea. Anyone else know? I just use Google.
It could probably use more text explaining what to do instead. I'd do that if I thought I knew <wink>.
Yes, that's exactly what I'm looking for: what is the current "blessed" procedure for using ZEO with Zope?
You can copy ZEO into lib/python or install ZODB into lib/python.
The client will be using the binary Zope 2.6.2 package, BTW.
I've (finally) read the ZODB page and it says Zope 2.6.2 doen't need a ZODB surgery to use ZEO. This is good since I don't want to scare the client with weird surgeries for a Production installation :-) (I'm mentoring them on the installation, not installing it for them).
Since we'll be using python-2.1.3, ZODB 3.2 isn't an option. Does ZODB 3.1.4 (the last ZODB release according to the ZODB3.1 page) fix the "one client changes an object but the others don't see the change" bug reported here recently?
It does. There are a few memory leaks and a potential deadlock bug that are only fixed in ZODB 3.2, but the majority of the critical bugs were fixed by 3.1.4.
If yes, should I just copy over the ZEO package or do you guys still recomend that I replace all of Zope262 ZODB with the standalone one?
Either one is fine with me. Jeremy
[Jeremy]
... On the other hand, Jim asked me today how someone would navigate from the zope.org home page to the current ZODB release. I don't have any idea. Anyone else know? I just use Google.
There are several ways, probably the easiest starting from the Developers/Zope Projects link in the left-side navigation bar, then following the ZODB link. Another easy way is to type ZODB in the Search box, then follow the top result. A more circuitous route starts with Download/Zope Products. But I use Google instead of site navigation aids on all public sites now, so those are the *last* things I'd try <wink>.
On Thursday 02 October 2003 19.50, Jeremy Hylton wrote:
On Thu, 2003-10-02 at 13:34, Leonardo Rochael Almeida wrote:
I thought that was easy to miss, so I changed the heading from
Zope Enterprise Objects
to
Zope Enterprise Objects (OBSOLETE)
And I still missed it! Amazing! it must've been the pre-lunch hunger or something... Maybe you should use a blink tag and a red font tag inside a one cell table with a thick border (/me runs from the HTML-standards mob).
Maybe we should just delete it.
Add a new release, version "obsolete" or something. People always get the latest release. Or add a meta refresh to redirect after 1s to the new page. -- /Magnus
Jeremy Hylton wrote at 2003-10-2 13:50 -0400:
... On the other hand, Jim asked me today how someone would navigate from the zope.org home page to the current ZODB release. I don't have any idea. Anyone else know? I just use Google.
The W3C has quite a good scheme: a fixed URL always points to the current release. Dieter
On Thu, Oct 02, 2003 at 12:02:32PM -0300, Leonardo Rochael Almeida wrote:
Hi,
I'm with a client in the process of setting up a production environment with ZEO.
Which of the ZEOs should I use?
* Old (t)rusty ZEO 1.0?
nope
* ZEO 2.0?
nope
* any one of the ZEO releases at http://www.zope.org/Products/ZEO ?
nope
* a ZEO ripped off of a ZODB release? Which one? (maybe even this last RC?)
Yes! Use ZEO from at least ZODB3-3.1.2. I know that one is good, I can't speak to later releases.
* In this case, should I make the ZEO server out of this ZODB release or should I just combine the ZEO server part into Zope and serve ZEO out of that?
the latter... just copy the ZEO directory into zope_source/lib/python/
* If use a standalone ZODB release as ZEOServer, can/should I run it on Python2.2 While using Python2.1 ZEOClients? (I'm not running Zope 2.6.2 on Python 2.2)
no idea, sorry. I still use python2.1.3 for everything zope-related. -- Paul Winkler http://www.slinkp.com Look! Up in the sky! It's NIHIL COOKIE WITH AN ATTITUDE! (random hero from isometric.spaceninja.com)
participants (6)
-
Dieter Maurer -
Jeremy Hylton -
Leonardo Rochael Almeida -
Magnus Heino -
Paul Winkler -
Tim Peters