Wayne Larsen wrote: > I have not looked at "ModPythonAppServer", but > embedding Webkit into Apache sounds like a much > improved solution. > > For those people with a dedicated server (or control > over a server), then running the AppServer as a > seperate process is not that big an issue. For > everyone else, however, it is a strong deterrent. > Getting a host provider that will host such a solution > is not simple, and you still have to deal with > starting the AppServer on server reboots (and in my > case managing the process without knowledge of the > process id, but that's a separate question). > > From what little I know about FastCGI from fixing it > to get it working as an adapter, it seems like it > would provide 90% of the solution of avoiding the > seperate AppServer process - managing the starting and > stopping of the appserver process, and the > communication of requests and responses. > > So to reframe Geoff's question - does anyone have the > AppServer embedded into apache, or have an idea of the > problems with such an approach, whether via > mod_python, mod_webkit, or fastcgi?
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
