- contexts become "applications" - get their own sessions and state;
I definitely want to support multiple applications living in the same process. Contexts don't really help me do that, though. So I'd rather simply have per-directory (or per-url-path) configuration. Then an application could simply be dumped somewhere, or the directory could be pointed to from some configuration file, and that would be it.
by any other name :-) could there be per-"application/directory/context/whatever" sessions and state with this approach?
The Context's __init__.py will be loaded, and I think some method from that called (contextInitialize or something).
would that method be passed a reference to server- and context-wide storage, so the the startup code could create and store objects there?
how about a similar one for server startup / storage that isn't logically related to any one context?
- out-of-the-box connection pooling
Is there anything wrong with MiscUtils.DBPool? At least, stuff that couldn't be fixed?
i think once there is server- and context-level storage and startup code, my confusion over this would go away. the dbpool could be created in the startup code and stored with the server or context, as appropriate.
(sorry if my terminology or grasp of webware is off - i'm still a bit new to it and am just starting to look at the source code.)
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
