Bill Moseley wrote:
At 02:02 PM 02/26/01 +, Steve Hay wrote:
I have a script which I wish to run under either mod_perl or CGI which does
little more than display content and I would like it to stop when the user
presses Stop, but I can't get it working.
You need to do different things
Hi,
Stas Bekman wrote:
Apache 1.3.6 and up -- STOP pressed:
the code keeps on running until it tries to read from or write to the
socket. the moment this happens, the script will stop the execution, and
run cleanup phase.
I think it's the same under mod_perl and mod_cgi. Am I right?
I
At 02:02 PM 02/26/01 +, Steve Hay wrote:
I have a script which I wish to run under either mod_perl or CGI which does
little more than display content and I would like it to stop when the user
presses Stop, but I can't get it working.
You need to do different things under mod_perl and
On Sun, 11 Feb 2001, Bill Moseley wrote:
I don't know why I have to learn this fresh again each time -- it appears
I'm confusing mod_perl and mod_cgi.
Let's see if I have this right. Under mod_perl and apache = 1.3.5 if the
client drops the connection Apache will ignore it (well it might
At 08:43 AM 02/12/01 +0800, Stas Bekman wrote:
What happens to the 54 earlier processes, since I submitted the request
55 times? How do Apache mod_perl handle the processes to nowhere?
They get aborted the first moment they try to send some output (or read
input if they didn't finish yet) and
I don't know why I have to learn this fresh again each time -- it appears
I'm confusing mod_perl and mod_cgi.
Let's see if I have this right. Under mod_perl and apache = 1.3.5 if the
client drops the connection Apache will ignore it (well it might print an
info message to the log file about
