All good points that I had not really thought about. With WebKit embedded in Apache with the FastCGI configuration that I can envision, you would have as many AppServers started that the demand and configuration call for (the configuration seems to be similar to webkits min/max/initial thread count).
This could be a serious issue for memory use - I haven't progressed far enough to know how much of an issue this is but I am concerned - anyone want to offer their typical appserver memory requirements for a large running application? Also a good point on the session store - I see a session affinity patch on the fastcgi page (albeit for an out of date version of fastcgi) that could solve this problem by redirecting users to the same appserver. An as an added bonus, it would remove the SkunkWEB claim that because of the python global interpreter lock, webware will not utilize much more than 1cpu in a multiprocessor configuration (has this been demonstrated?) I certainly haven't seen any host providers using Apache 2 yet, although that's might be an interesting solution. Wayne > > A big disadvantage of embedding WebKit into Apache > is that Apache (version > 1.X and by default, version 2.X) spawns multiple > processes to handle > requests. But one of the advantages of WebKit is > that it runs in a single > process, allowing you to cache data at the > application level, store sessions > in memory, etc. > > So this means that embedding WebKit within Apache > will generally cause > multiple copies of WebKit to be running. This is > much less efficient from a > memory standpoint, especially if you like to write > your servlets so that > they cache a lot of data in memory. Also, it would > require you to use the > FileSessionStore, which is less efficient than the > in-memory stores (it must > pickle and unpickle the session to disk on every > request) and more > importantly, has concurrency problems (one copy of > WebKit can potentially > overwrite session data changes that were made by > another copy of WebKit, > since they aren't sharing the same session objects > in memory) that can cause > subtle bugs. > > With Apache 2.0 there might be the possibility to > configure Apache to serve > requests from a single process using > multi-threading. This might allow you > to avoid the problems of multiple copies of WebKit. > On the other hand, how > many host providers actually use Apache2, and would > let you configure it > exactly as needed? > > - Geoff > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Webware-discuss mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/webware-discuss __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
