> On my Mac Server I used Screen Sharing to start web2py, and run web2py > as a long running process, that is, I didn't 'kill' it. How does that > work at WebFaction > is web2py started everytime there is a request an then stopped?
This happens ONLY if you use cgihandler.py. It does not happen with any of the other handlers. For example if you use mod_wsgi, Apache starts Python and it is loaded in the memory with all web2py modules. At every request gluon.main.wsgibase is called. Threads are recycled and database connections are recycled for speed. Because web2py is not reloaded cache.ram is persistent and shared across requests as long as you do not restart apache. Massimo -- You received this message because you are subscribed to the Google Groups "web2py-users" group. To post to this group, send email to web...@googlegroups.com. To unsubscribe from this group, send email to web2py+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/web2py?hl=en.
