Tim Roberts wrote: > That's fascinating. Among the handful of Webware sites I've done, one > is a commercial real estate site that averages about 30,000 hits a day > and sends about 10,000 subscriber e-mails per day. It's been up 420 > days without any server maintenance at all. Since moving to 0.8, I > have seen zero stability problems with Webware. The try/except > handling is good enough that exceptions cause well-controlled error > pages with e-mail notifications -- they don't bring down the server. > > I do appreciate the advantages of the one-hit CGI model, but I don't > think Webware suffers much without it.
Webware itself seems totally stable. However, you are always at the mercy of whatever C-coded extension libraries you are using. One bug there and either your whole process goes down, or your threads get wedged one at a time until there are no threads left available to handle requests. That's the advantage of a multi-process model -- an unstable extension library is much less harmful. But if Webware were to use a multi-process model, you would lose the ability to efficiently cache SQL results in memory for all servlets to share. I would have a hard time giving that up. - Geoff ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Webware-discuss mailing list Webware-discuss@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/webware-discuss
