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
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 mod_c
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
Hi,
Is this the thing you want?
(otherwise please describe your problem more elaborately.)
print
"Content-Type: text/html\n\n";
print
"html message here";
print "\n";
print
"html message here";
Bye
Muthu
S Ganesh
-Original Message-From:
[EMAIL PROTECTED]
[
Hi there,
On Fri, 16 Feb 2001, Kiran Kumar.M wrote:
> I would like to know what header to print to view this on the browser
Your question is not very clear, are you using mod_perl? If so how is
it configured? Have you read .../mod_perl/SUPPORT? Have you seen the
Eagle Book? Have you read th
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 mi
Yes, I remember Gunther recommending the javascript approach a while back, and I think
it is a good solution, but I just can't stand javascript. I always surf with it turned
off, because it frequently causes my browser to hang. It's a personal hang-up.
I was really interested in just learning h
If youre looking for a solution, i suggest putting in a little javascript
on the form..
...
as for the other processes, its been my experience tha
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 "br
[EMAIL PROTECTED] (Buddy Lee Haystack) wrote:
>Situation:
>I press the submit button on a form 55 times in 15 seconds. Each
>request would normally return data to the browser within ten seconds
>due to the time it takes the database query to execute.
>
>
>Question:
>What happens to the 54 earlier
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)
On Sun, 11 Feb 2001, Buddy Lee Haystack wrote:
> Situation:
> I press the submit button on a form 55 times in 15 seconds. Each request would
>normally return data to the browser within ten seconds due to the time it takes the
>database query to execute.
>
>
> Question:
> What happens to the 5
12 matches
Mail list logo
