From: Rob McCool <robm@netscape.com> Newsgroups: netscape.devs-nsapi Subject: Re: Reload button behavior Date: Thu, 24 Oct 1996 18:20:04 -0700 When the user presses reload, the CGI that was running should be getting a SIGPIPE and the new CGI should start. To my knowledge the CGIs do not share any pipes, connections, or resources that would cause what you describe. It's possible that this is simply an interaction between the operating system and the network, what OS are you running?--Rob
Erick Rudiak wrote: > > Dear Netscape Developer Gurus - > > I am currently on a project that is using Netscape Enterprise > Server 2.0 to build a web-enabled transactional system. While we have > succeeded in trapping SIGPIPE from the server when the user presses back, > stop, forward, home, etc..., we do not receive any signal when the user > presses the Reload button. In fact, a second (third, fourth, etc...) > copy of the CGI is started up, and apparently it uses the same socket > connection as the previous invocations (we are assuming this because > starting any subsequent CGI does not cause SIGPIPE to be sent, but > pressing stop during the last CGI sends SIGPIPE to all CGIs that are > running for that request, not just the last one). It is critical that we > are able to trap the reload button, since the transactional system will > turn quite ugly if multiple requests for the same "pending" transaction > are submitted. Is there a way to trap, and thus handle, the user's > pressing of the Reload button either in the CGI itself, or through the > server API (which seems to have some knowledge of this event since it > knows to send only the output from the last CGI invoked through the > socket, even though all the CGIs that run concurrently seem to have it > open). > > If you know of a solution, or could point me at an FAQ, etc., I > would be quite grateful. Thanks for your help! > > Erick Rudiak > Hewitt Associates LLC > 847 295-5000 x14573
-- Rob McCool, robm@netscape.com http://home.netscape.com/people/robm/ Stunt Programmer, Netscape Communications Corporation It was working ten minutes ago, I swear...Reproduced by permission of the author.