Hi, I'd like to point out that as you've stated, django is deployed in mulit-threaded environments successfully, employing an app that makes use of geodjango in a multi-threaded environment is not. Justin (Bronn) will testify to this I'm sure (as I and others have run into this issue whilst attempting to deploy mod_wsgi/mod_python/others in a mutli-threaded environment. (This is due to the underlying libgeos c library not being thread safe itself)
I should (and will) create a ticket to make this clear in the django docs for the geodjango parts, so that others may avoid the pain we went throught a few months back. Cheers, Matt 2008/11/17 Jacob Kaplan-Moss <[EMAIL PROTECTED]> > > On Mon, Nov 17, 2008 at 10:54 AM, Ludvig Ericson > <[EMAIL PROTECTED]> wrote: > > There are bugs. Django isn't thread-safe, and we know that. > > Um... > > That's just not true. At one point (two years ago?) it wasn't, but > these days Django's deployed all over the place in mutli-threaded > situations. If it wasn't threadsafe we'd hear about it. > > Jacob > > > > -- Cheers, Matt --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
