Marc Battyani <Marc.Battyani@fractalconcept.com> wrote:
+---------------
| mod_lisp 2.3 ... The major improvement is to force Apache to
| read all the Lisp reply before eventually closing the socket.
| This should avoid writing to the Apache process when it has
| closed because the client browser has closed the connection.
+---------------

Just curious...

1. Does this in any way affect the ability (very important in
   some applications!) to "stream" data through Apache to the
   client browser, so that the beginning of the output gets to
   the browser early to give the user something to look at while
   the rest is being computed (e.g., with a slow database access)?

   I don't think it *has* to -- you could be simply "draining
   the pipe" if the client aborts -- but I wanted to check.

2. What are the implications for a "runaway" Lisp process that
   generates infinite output? Normally when that happens and
   the user (say) manually hits "Stop" (aborting the connection),
   the abort would propagate back to the Lisp process as a
   SIGPIPE (which could be caught & handled), would it not?
   Have you perhaps traded one evil for another?


-Rob

-----
Rob Warnock, PP-ASEL-IA		<rpw3@rpw3.org>
627 26th Avenue			<URL:http://rpw3.org/>
San Mateo, CA 94403		(650)572-2607