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 how the server handled it, and Stas squared
me away. My fear was that it would cause my server to hang, which was my usual
experience under Windows NT, but my Linux box just slows to a crawl, and doesn't hang.
I can live with that. :)
Have a good night!
Mike Wojcikiewicz wrote:
>
> If youre looking for a solution, i suggest putting in a little javascript
> on the form..
>
> <FORM blah onSubmit="return submitme();">
> ...
> <script language="JavaScript">
> <!--
> var clicked = 0;
> function submitme() {
> if(clicked == 0) { clicked = 1; }
> else { return false; }
> return true;
> }
> //-->
> </script>
>
> as for the other processes, its been my experience that they complete and
> die off after apache is done... ie lagging your server to hell.. depends
> on your configuration though
>
> Michael Wojcikiewicz
> Web Application Developer
> E-Mail: [EMAIL PROTECTED]
> ICQ: 944221
>
> 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 54 earlier processes, since I submitted the request 55 times?
>How do Apache & mod_perl handle the processes to nowhere?
> >
> > Thanks!
