Malcolm Tredinnick wrote: > The development server is only single threaded. So one request at a > time. Since requests include each and every stylesheet, every image, > etc, that can be quite a number of requests per page.
Can or will this ever change? If I understand correctly, the base WSGI web server implementation (in django/core/servers/basehttp.py, class ServerHandler) is multi-threaded (or at least it has the variable that suggests so: wsgi_multithread = True). I'm not clear on what would have to change to make this happen. If all of Django would need to be changed to support a multithreaded environment than I can see that as being too much and for a small or unwanted gain. (Apache or other webserver typically handles the threading so why should Django?) But if it's some tweaks to the underlying included server...? > If there is ever a problem where one browser doesn't close the > connection completely, it will block all other requests. This shouldn't > happen (since it will only be speaking HTTP/1.0, so persistent > connections aren't available), but I've heard people mentioning that > they'd had IE not closing the connection completely. Completely > unconfirmed by me; may or may not be a real problem. I hadn't realized or thought about this. Thanks for bringing it up. > There is no really robust error recovery in the server: if your code > throws an exception, it may be sufficient to stop the server's main loop > (not all exceptions cause this, but it's possible to have this happen). I've seen this happen where the server just drops to the command prompt suddenly. We've got a case where we may want to try to create a self-contained Django instance to send to reviewers or clients. Not a production environment but something that can run easily on a desktop. Seeing some of these issues is enlightening. I think our approach might have been to write a wrapper script to launch something like Lighttpd for static files and Django for each page request on separate ports to make the page load look more responsive. For a single user on the desktop I think this might work but we haven't attempted or tested it yet. -Rob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users -~----------~----~----~----~------~----~------~--~---
