Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:29027 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 99527 invoked by uid 1010); 25 Apr 2007 20:48:38 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 99511 invoked from network); 25 Apr 2007 20:48:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Apr 2007 20:48:38 -0000 Authentication-Results: pb1.pair.com smtp.mail=ceo@l-i-e.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=ceo@l-i-e.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain l-i-e.com from 67.139.134.202 cause and error) X-PHP-List-Original-Sender: ceo@l-i-e.com X-Host-Fingerprint: 67.139.134.202 o2.hostbaby.com FreeBSD 4.7-5.2 (or MacOS X 10.2-10.3) (2) Received: from [67.139.134.202] ([67.139.134.202:2734] helo=o2.hostbaby.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 8B/30-00993-5AEBF264 for ; Wed, 25 Apr 2007 16:48:38 -0400 Received: (qmail 59053 invoked by uid 98); 25 Apr 2007 20:48:38 -0000 Received: from 127.0.0.1 by o2.hostbaby.com (envelope-from , uid 1013) with qmail-scanner-2.01 (clamdscan: 0.88.7/3160. Clear:RC:1(127.0.0.1):. Processed in 0.076213 secs); 25 Apr 2007 20:48:38 -0000 Received: from localhost (HELO l-i-e.com) (127.0.0.1) by localhost with SMTP; 25 Apr 2007 20:48:38 -0000 Received: from 216.230.84.67 (SquirrelMail authenticated user ceo@l-i-e.com) by www.l-i-e.com with HTTP; Wed, 25 Apr 2007 15:48:38 -0500 (CDT) Message-ID: <59552.216.230.84.67.1177534118.squirrel@www.l-i-e.com> In-Reply-To: <10845a340704250821v28b0b7f6v1b08a7937727c113@mail.gmail.com> References: <10845a340704250821v28b0b7f6v1b08a7937727c113@mail.gmail.com> Date: Wed, 25 Apr 2007 15:48:38 -0500 (CDT) To: RQuadling@GoogleMail.com Cc: "internals" Reply-To: ceo@l-i-e.com User-Agent: Hostbaby Webmail MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: [PHP-DEV] Killing an ISAPI thread. From: ceo@l-i-e.com ("Richard Lynch") On Wed, April 25, 2007 10:21 am, Richard Quadling wrote: > Running PHP via ISAPI on Sambar Server. > > I have a script which is allowed to take a long time. > > The user has an Abort option and via clever use of sessions, the > script can be terminated. [This answer probably belongs on php-general, but does not directly address the apropos question.] I suspect that you may want to do some serious browser-compatibility testing here... It's possible that the "stupid" users are the ones using a browser in which your Abort process simply doesn't work. You might also want to consider converting the whole thing over to a "job" oriented model. Users submit "jobs" and they are processed, perhaps piece-meal, until finished. Once you have it "job" oriented, it gets a lot easier to manage long-running jobs, notifiy users of status, etc. And then NOBODY has to sit there waiting for too long, and your HTTP connections are freed up to do something useful. Tying up the relatively expensive HTTP connection for a long-running process that requires no human interaction is kinda silly, usually. :-) -- Some people have a "gift" link here. Know what I want? I want you to buy a CD from some indie artist. http://cdbaby.com/browse/from/lynch Yeah, I get a buck. So?