Perhaps. I definately agree on the performance aspect. My personal concern is a stability one. Basically I just dont believe the servlet model can offer the same sort of stability that the one-hit page model can, principally because on a php page, if the code raises an exception, it'll flatten the page, not the server. There can also be issues with locking , 'leakyness' (not *really* as big a problem with python, but I've seen it in java servlets despite the touted magic of garbage collection).
Finally I do believe webware is not too hard to kill. I'm sadly having to
reboot the webware install I maintain pretty regularly.
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.
-- - Tim Roberts, [EMAIL PROTECTED] Providenza & Boekelheide, Inc.
------------------------------------------------------- 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
