Hello, Has anyone put thought into using a couple extra threads in a mod_wsgi to handle background tasks (similar to how many of us use cron)? Ideally this would cover multi-process, multi-server scenarios, so one would need a method of synchronizing the "worker threads" (database, etc...).
If during the startup of a given mod_wsgi process (daemon mode), a couple of python threads were spawned... 1. are there any fundamental issues with that? 2. are there any restrictions to be aware of (signals come to mind)? 3. with proper exception handling, could that be a highly reliable solution? To me it would be great to cut crontab out of the loop, and run everything in the same environment. When your app is running (because Apache will make *sure* it is running with a high degree of confidence), then your background processes are doing their thing also. Just looking for advice and feedback. Thanks! Jason Garber -- You received this message because you are subscribed to the Google Groups "modwsgi" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/modwsgi?hl=en.
