Fair point :) I have an application with a ZODB. Some parts of the app will require complex calculations that will take a really long time to run. After they finish, they'll want to write something. So i essentially imagine something like this:
- Pyramid frontend, read access - Celery long running tasks with read access. - Celery write tasks The rationale for this is that the ZCatalog doesn't handle conflict resolution well, so I'll want the write tasks to be queued and written in sequence. Also, I want all the write tasks to use their own transactions. This is currently accomplished by creating a new request before the task is run, and running the closer when it's finished. That seems to cause a memory leak though. Anyone doing something similar? Thanks a lot, Robin 2015-11-18 18:06 GMT+01:00 Jonathan Vanasco <jonat...@findmeon.com>: > What exactly are you trying to do with Celery - can you give an example? > > -- > You received this message because you are subscribed to the Google Groups > "pylons-devel" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to pylons-devel+unsubscr...@googlegroups.com. > To post to this group, send email to pylons-devel@googlegroups.com. > Visit this group at http://groups.google.com/group/pylons-devel. > For more options, visit https://groups.google.com/d/optout. > -- Betahaus phone: +46 70-333 00 10 web: http://www.betahaus.net -- You received this message because you are subscribed to the Google Groups "pylons-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-devel+unsubscr...@googlegroups.com. To post to this group, send email to pylons-devel@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-devel. For more options, visit https://groups.google.com/d/optout.
