On Fri, Mar 18, 2011 at 1:36 PM, Roberto De Ioris <[email protected]> wrote:
> > >> > > > > This would be awesome of you. Thanks. > > > > > >> - > > > So a user requests > > /one/two.py > > uWSGI will load the /one/two.py file (it contains a 'application' > callable) and it will execute it leaving it in memory. The next request > will be served from uWSGI memory. > Yep > > Every .py file will be an app in uWSGI instance. > > You plan to have a uWSGI instance for every domains, or one for all ? > Preferably one for each domain but I can't see that happening in any sort of automated fashion easily. > > If you choose one for all remember that security problems will raise all > over the place. > Noted > > Another part is reloading, i suppose you do not give shell access to your > users, so every app should monitor the .py file for changes (or probably > it is easier to unload the app after every request build a cgi-like > system) > Is this possible? I think I may need to rethink my approach a little bit but I'd like to see where discussion leads. -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
