I think Tim meant this to go to the list ;-)
Chris
Original Message
Subject: Re: [Zope-dev] Browser Stop Button and Zope REQUESTs
Date: 29 Aug 2002 14:36:30 +0800
From: Tim Hoffman [EMAIL PROTECTED]
To: Chris Withers [EMAIL PROTECTED]
References: [EMAIL PROTECTED
On Thu, 29 Aug 2002 11:41:44 +0100, Chris Withers spoke forth:
Original Message
Subject: Re: [Zope-dev] Browser Stop Button and Zope REQUESTs
Date: 29 Aug 2002 14:36:30 +0800
From: Tim Hoffman [EMAIL PROTECTED]
If my ZODB is so big that it takes half an hour to rebuild, I
Christopher N. Deckard wrote:
Oh, and back on the original topic, does anyone know for sure if
the browsers actually send something to the server when stop is
pressed?
Yes, it sends a RST packet. It ends the tcp-connection.
That's why I think throwing an exception when something tries to
On Thursday 29 Aug 2002 2:21 pm, Oliver Bleutgen wrote:
If something like I described would be implemented into zope, it surely
should be possible to start an extra thread for doing the stuff you give
as an example
The issue is that zope *already* runs *every* request in a seperate thread
I know I'm late in on this thread, but I thought I'd throw in my views.
I'd like to see the REQUEST be flat plain aborted when someone hits the stop
button or the connection dies.
I don't is the is context.REQUEST.RESPONSE.isClientConnected() really working.
How would I plug this in an
Chris Withers wrote:
I know I'm late in on this thread, but I thought I'd throw in my views.
This is very nice, it seemed like nobody was interested in that.
I'd like to see the REQUEST be flat plain aborted when someone hits the
stop button or the connection dies.
Yes, that would be the
Oliver Bleutgen wrote:
Mod_perl also seems _not_ to stop a long running script if this script
doesn't try to write to the RESPONSE (or whatever they call it). The
perl test script I posted does write output, and this causes it to stop.
If I try a script with no output, it never gets
Steve Alexander wrote:
Oliver Bleutgen wrote:
Although Zope has a response stream method of sending information back
to the client, most things in Zope don't use it.
Instead, the response information is aggregated, converted into a
string, and then sent back all at once at the
FWIW, I just checked in a signal handler to the trunk that makes it
possible on UNIX to do kill -USR1 `cat var/Z2.pid` and pack the
database to 0 days, so all this business about packing TTW and whether
you need to let the browser wait or not is for naught. ;-)
On Wed, 2002-08-28 at 07:49, Chris
