Daniel Roseman wrote:
With mod_wsgi it could even be multithreaded, though threading requires a certain level of developer sophistication to be safe.This isn't a question about Django, but about WSGI deployment.Although I must say I'm confused, you say you're using WSGI but you're printing something, so it seems like you're using the development server since that prints to the console? Is this right? If so, you can't do this, as the development server is single-process. When properly deployed on Apache via mod_wsgi, it should be multi-process.
Another tidbit - a print to stderr, or output through Python std logging, will make its way into the Apache error logs, or at least it does on our installations.
If you are definitely already using mod_wsgi, you'll need to post your Apache configuration. -- DR.
-- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
<<attachment: rmela.vcf>>