On Nov 16, 4:40 pm, Chris <[EMAIL PROTECTED]> wrote:
> I understand what you're saying. It's just unfortunate we're throwing
> out the convenience of the dev server.
>
> What's up withhttp://code.djangoproject.com/ticket/3357? Looks like
> this idea isn't new.
Using daemon mode of mod_wsgi can almost give you the convenience you
want. The main issue with Apache is generally the need to restart
Apache on all code changes. With mod_wsgi daemon mode, you only need
touch the modification time of the WSGI script file after a set of
code changes have been made and mod_wsgi will ensure application is
reloaded. If you want, you can add your own monitor thread which looks
for changed files and automatically triggers an application restart.
See:
http://code.google.com/p/modwsgi/wiki/ReloadingSourceCode
Graham
> Chris
>
> On Nov 16, 12:30 am, Malcolm Tredinnick <[EMAIL PROTECTED]>
> wrote:
>
> > On Sat, 2008-11-15 at 21:17 -0800, Chris wrote:
> > > Do you mean easier in that runserver doesn't support multithreading at
> > > all? Or easier in that it supports multi-threading, but it's difficult
> > > to set up?
>
> > The dev server is single-threaded by design. It wouldn't be impossible
> > to make it multi-threaded with code changes, but it would be fiddly and
> > in the past we've said we really aren't interested, since it adds a lot
> > of maintenance burden. If you want multi-threaded behaviour, use a real
> > web server.
>
> > Regards,
> > Malcolm
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---
