2009/3/20 Florian Bösch <[email protected]>: > > On Mar 20, 12:05 pm, Graham Dumpleton <[email protected]> > wrote: >> Must have mod_wsgi 2.X. Then read: >> >> http://code.google.com/p/modwsgi/wiki/ReloadingSourceCode >> >> with further examples highlighting just this in: >> >> http://blog.dscpl.com.au/2008/12/using-modwsgi-when-developing-django... >> http://blog.dscpl.com.au/2009/02/source-code-reloading-with-modwsgi-o... > > These urls propose setting up a monitor that kills the daemon or > having a special reload handler in your app. > > This is not what I asked. I asked how I can restart the process upon > *any* http request intended for a wsgi script under the condition that > any file has changed and serve the request that triggered the kill > with the freshly loaded process.
You can't. What I pointed you at is the best you are going to get. The use of a monitor thread like that is the same technique used by most Python development servers, eg. Django runserver. Why is the use of a monitor thread unacceptable? The examples shown perform the check once a second which should be sufficiently fine granularity for development work, and imposes a lot less overhead than having a check made of every single loaded file on every request. Graham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "modwsgi" 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/modwsgi?hl=en -~----------~----~----~----~------~----~------~--~---
