> -----Original Message----- > From: Jeff [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 15, 2002 3:24 PM > To: [EMAIL PROTECTED] > Subject: CGI Timeout > > > This may be as much a question about web servers as it is > about perl cgi. Sorry if you find it inappropriate. > I am having a hell of a time with CGI Timeouts on the client > side of things when I have database intensive, long-running > processes on the server side. I have increased every single > timeout parameter I can think of. > I am running IIS on a Windows 2000 server machine and > executing activeperl cgi scripts. The scripts fun fine for > short requests via the browser and the scripts run just fine > if executed from the command line. This is just a small > application for 10 or so users to execute database transactions. > The CGI timeout error actually stops the process on the > server side. I would at least like to get to a point where > the users may receive a timeout, but the perl cgi keeps > running on the server side until it successfully completes > its processing. There are WAY too many input variables for > this to be spawned as a seperate process via a "system" call. > The input array can sometimes be up to 4000 elements.... > Any thoughts?????? > Thanks, > Jeff
Spawn the separate process with fork(). The parent can emit a response and exit, while the child continues on with the processing. merlyn also posted the following link a few days ago with a fancier approach to this kind of problem: http://www.stonehenge.com/merlyn/WebTechniques/col20.html -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
