At 02:55 PM 2001.06.25 -0400, you wrote:
>I am running a CGI script on IIS that takes a while to run (10-15 minutes)
Egad, that's a long time. Are you sure that conventional CGI is the best way to do
this? It sounds like keeping the user & browser waiting for this long might not be the
best idea. Would it be possible to break apart the output, so that the user
immediately gets shown a page saying that the process has begun, and then when it
completes the process lets the user know by sending out an email? That followup mail
can state either that things went smoothly and the results are available either as
part of the message or online at $url, or if anything wrong the mail can say so.
Either way, you get to sidestep the wait issues you're dealing with.
Alternatively, it looks like the LWP::UserAgent module *might* be able to help you. It
provides a method $us->timeout([$secs]), which allows the web client to set a timer
(in seconds, defaults to 180 secs). I don't think this would necessarily help unless
you're embedding that code into a web client manually, which you don't seem to be
doing. If there's an equivalent method in CGI.pm, at a glance, I can't find it.
Failing that, you could either try configuring your web server to extend the timeout
settings (can't help you if you're using IIS -- I only deal with Apache), or you could
try having the script "trickle out" some data just so that the client doesn't think
the connection has died.
Those are still kludgey though -- detaching the process & letting it run with a
closing email seems like a much cleaner solution...
--
Chris Devers [EMAIL PROTECTED]
_______________________________________________
Perl-Win32-Admin mailing list
[EMAIL PROTECTED]
http://listserv.ActiveState.com/mailman/listinfo/perl-win32-admin
