Sorry, I forgot to post the url to the fastcgi docs http://www.djangoproject.com/documentation/fastcgi/
On Mar 29, 7:52 pm, Eric <[EMAIL PROTECTED]> wrote: > I currently use lighttpd and fastcgi, and I noticed that in the django > documentation that they mention using threaded instead of prefork when > running your fcgi server. > > I had the same fears and I used prefork first, but after some load > testing of both, I decided to use threaded. I'm a brave soul and I > assumed that if the documentation prefered threaded, it was safe. > > Generally your pretty safe with threading unless you're using module > level or global variables. > > I hope that helps. > > Eric. > > On Mar 29, 3:26 pm, Peter Rowell <[EMAIL PROTECTED]> wrote: > > > > The best I have ever been able to get out of anyone associated with > > > Django development about thread safety is the comments by Jacob Kaplan- > > > Moss in the following thread: > > > Sigh. Reading through that thread was singularly unsatisfying. I guess > > that, for the moment, I'll have to stick with prefork. > > > If Django, minus any DB-related issues, is thread safe, and if the > > supplied apps (auth comes to mind) are written correctly, then perhaps > > Django-out-of-the-box could be declared thread safe. > > > Some appropriate warnings/suggestions could be put in the docs. Maybe > > point out user operations that could pose a problem and suggest > > possible ways to handle them. > > > Thanks again, > > Peter --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" 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/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
