On 18.03.2014 14:08, Chris Rossi wrote: > It should start its own connection via the standard ZODB API. You might > consider moving the extra work to a different process. Redis pub/sub or > list objects are good ways to communicate and set up a primitive, simple > queue. I prefer that to more complex queue/messaging frameworks. YMMV.
Right now I have no ZEO running. In Production there will be a ZEO but while developing a ZEO server simply adds to complexity and makes debugging even more pain in the ass. It might solve me problem if I could start a worker thread at application start an send the task via queue there but there is still the problem to get a thread with access to the zodb started. I know that it's possible to use one ZODB connection in multiple threads, Zope does it and pyramid does it. The question is how to fork a new subconnection or transaction and pass it to the new thread. Regards Estartu -- ---------------------------------------------------------------------------- Gerhard Schmidt | http://www.augusta.de/~estartu/ | Fischbachweg 3 | | PGP Public Key 86856 Hiltenfingen | JabberID: [email protected] | auf Anfrage/ Tel: 08232 77 36 4 | | on request Fax: 08232 77 36 3 | |
signature.asc
Description: OpenPGP digital signature
