managing asynchronous jobs from pyramid; module-level variables and wsgi

[Jasper van den Bosch]

My pyramid app has some work that it should start as an asynchronous job (after the response has been returned);  downloading a remote file and processing it, etc. Celery seems a bit overkill at this point.

So I've been looking at jdnavarro's async demo http://dannynavarro.net/2011/01/23/async-pyramid-example-done-right/

But it seems to depend on module-level variables to share the Queue with other requests. According to the mod_wsgi documentation,

http://code.google.com/p/modwsgi/wiki/ProcessesAndThreading#Python_Sub_Interpreters

 this is not dependable when using mod_wsgi. So am I correct that I would need some database or filesystem-based approach to manage the jobs globally? How did others solve this?

Thanks,

Jasper

http://ilogue.com

jas...@ilogue.com