On Friday 06 June 2003 10:29, you wrote:
>But maybe it's simpler and more reliable just to put in a bare >bones http get implementation
For people using aolserver as http-server, well, ok. But there are others, not necessarily employing it as http-server at all. I think in order to have a general solution, one should at least allow some limited scripting capabilites for the watchdog, if need be. On the other side, having the watchdog as simple is possible is equaly (if not more) important.
It's my perception that several AOLserver problems have been due to underlying problems with Tcl. I would want the parent process to be (almost) provably correct and if there is a problem, I would want it to be easy to find with inspection.
To support the non-http users (of which I am one from time to time), I'd prefer to see a plug-in architecture similar to the db and comm modules. Support http-get-monitoring with a plug in and let others develop their own X-Y-monitoring with plug ins of their own.
Leave Tcl out of the parent and we can be assured the parent is still robust and invariant to new versions of Tcl.
Jerry
-- AOLserver - http://www.aolserver.com/ To Remove yourself from this list: http://www.aolserver.com/listserv.html List information and options: http://listserv.aol.com/
