On Mar 20, 12:26 pm, Graham Dumpleton <[email protected]>
wrote:
> You can't. What I pointed you at is the best you are going to get.
I could If I wrote my own wsgi webserver. I can't is not good enough.
> Why is the use of a monitor thread unacceptable?
When doing development I don't want my code to bounce up and down
until I've done editing. Everytime an Application gets instantiated
there might be arbitary things going on like connecting to a database,
retrieving schemas etc. There is a button on my browser that says
reload. When I press that button I've done editing. That should be
enough.
> 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.
Right. I've hacked up some configuration now that wipes a set of
configured modules from sys.modules and re-imports the whole bunch
upon every request. That's fine enough for me and still fast enough. I
don't see that checking files would be such a grand overhead.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
