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.
In my experience, success is entirely based on whether you hit threading issues or not. If you don't have threading problems -- particularly in your extensions (e.g., a database driver), or your OS (i.e., RedHat) -- then you should find Webware to be very stable. But if you do encounter threading problems it sucks.
One bit of advise: I think it's best not to share C-based resources between threads. More specifically, not to share a database connection between threads, but instead key them with one connection per thread. This is how Zope does it, and it gets by pretty well with a threaded server.
-- Ian Bicking / [EMAIL PROTECTED] / http://blog.ianbicking.org
------------------------------------------------------- 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
