[Jeremy Hylton]
>> It's mentioned in the documentation -- see section 3.4 ZEO programming
>> notes -- and it's been discussed on this list many, many times.

[Chris Withers]
> Where are these notes?

    http://www.zope.org/Wikis/ZODB/FrontPage/guide/index.html

Then click on section "3.4 ZEO Programming Notes".

>> It sounds like the simplest approach for your application is to do like
>> Zope and start a separate thread that runs an asyncore mainloop. Then
>> your application threads will see updates when the commit and abort
>> transactions, just like the would in Zope.

> I'd really prefer not to do that unless absolutely necessary:
> http://mail.zope.org/pipermail/zodb-dev/2004-June/007554.html

You should read that entire thread, but on zope-dev, to which follow-ups
were set and where almost all discussion took place.  But I'm betting your
app doesn't call fork() to begin which, in which case nothing in that thread
has any relevance to your app. 

_______________________________________________
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/

ZODB-Dev mailing list  -  ZODB-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zodb-dev

Reply via email to