Deploying Django behind Apache is great for real web apps, but I also use Django for Desktop apps that employ a web browser as the UI. In this situation, a distribution package that depends on Apache is not an option (too much for end users to manage), and the Django development server's weaknesses (especially the one request at a time limitation) disqualify it.
I've had positive experiences with the standalone CherryPy webserver in other contexts, and I've seen it recommended for use with Django, BUT I'm having problems. Maybe once in every dozen page requests (each which might result in a dozen or more http requests) it appears that the CherryPy webserver loses the request, i.e. it never gets passed up the WSGI stack to Django. If I hit the browser's reload button, (usually) the resubmitted page request is handled OK. Although I can't prove it, I'm suspicious that the problem may be that Django is not thread safe. Can anyone state for a fact that it is safe to use Django with a multi-threaded webserver? If not, then multi- threaded webservers like the CherryPy server are not really candidates for use with Django. Is there a high quality, server that's light enough to be packaged with a desktop app or other turn-key app that has been vetted for use with Django? I've researched the python based servers I could find mentioned via Google search, but everything I've found is either unmaintained, multi-threaded, or severely crippled. Thanks. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
