[EMAIL PROTECTED] wrote: > One thing that has reportedly been problematic with Zope and > Webware is the choice of threads for distributing work and > the scalability issues that this brings with it. Having said > that, the threaded paradigm is probably so entrenched in the > average Webware application (or in power-user applications, > at least) that I can't see a process-oriented variant of Webware any > time soon.
I love the coding convenience that Webware's threaded architecture gives me. It makes caching things like SQL results in memory trivially easy. It's memory-efficient. And so forth. But there is a drawback. If there's a bug in any of your C-coded extension modules that causes the process to crash, it kills the whole app server including any other requests that were being processed. And then you lose all of the current sessions. This has bitten some people on this mailing list in the past because of bugs in database adapters. And right now I'm trying to track down a problem where I have a servlet that makes an HTTPS request to another web site (using Python's built-in SSL support), and it looks like every once in a while, something happens during that outgoing HTTPS request that crashes the app server. It only happens like once a week, so I haven't had any luck tracking this down. If Webware used some sort of process pool instead of a thread pool, and served only one request per process, this wouldn't be as much of a problem. - Geoff ------------------------------------------------------- This SF.NET email is sponsored by: eBay Great deals on office technology -- on eBay now! Click here: http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
