I'm a bit confused how multi-threading has anything to do with AJAX? Your requests will be slower, but they will still get processed (at least I've never had any issues).
On Nov 16, 1:03 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > If the patch that's currently on there works with no changes at all, > I'd be hesitantly in favor of it, however if there any bugs, or other > complications associated with it, my answer is to use a real server, > setting up something like CherryPy locally is almost no effort, as > seen > here:http://www.oebfare.com/blog/2008/nov/03/writing-custom-management-com... > > On Nov 16, 1:39 am, "Calvin Spealman" <[EMAIL PROTECTED]> wrote: > > > Does it need to be multi-threaded? Can you get a multi-process dev > > server instead/also? > > > On Sun, Nov 16, 2008 at 1:26 AM, Chris <[EMAIL PROTECTED]> wrote: > > > > I thinkhttp://code.djangoproject.com/ticket/3357shouldbe given > > > another look at enabling optional multi-threading on the dev server. > > > > Jacob previously closed this ticket, noting the patch could introduce > > > threading bugs, and would provide functionality too similar to that of > > > a production environment. > > > > This is my rationale to accept this ticket: > > > 1. Ajax is very common place, and often requires a multi-threaded > > > server. The dev server is very convenient, but by not providing multi- > > > threading support, we're preventing it from being even more useful. > > > 2. Since multi-threading would be an optional setting, the default > > > scenario would still be single-threaded and would not break anything. > > > Only those specifically desiring multi-threading would subject > > > themselves to any unforeseen bugs. > > > 3. Fear of multi-threading bugs shouldn't be a reason to avoid multi- > > > threading, especially when it could be very useful. We don't even know > > > if there are multi-threading bugs. And even if there are, they can be > > > fixed. > > > > Regards, > > > Chris > > > -- > > Read my blog! I depend on your acceptance of my opinion! I am > > interesting!http://techblog.ironfroggy.com/ > > Follow me if you're into that sort of > > thing:http://www.twitter.com/ironfroggy --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
