I think http://code.djangoproject.com/ticket/3357 should be 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 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
