[Fwd: Re: [Zope-dev] Browser Stop Button and Zope REQUESTs]

[Chris Withers]

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 <timhoffman@cams.wa.gov.au>
To: Chris Withers <chrisw@nipltd.com>
References: <3D66A3E5.5050302@gmx.net>	<001b01c24aea$6fa37060$6717a8c0@dorothy>		<3D66B042.1090900@gmx.net> <1030196732.1365.34.camel@james>		<3D67C9D7.4000501@gmx.net> 
<1030216329.1327.114.camel@james> 	<3D6CB8AD.40206@nipltd.com>

Hi


Just my 2c worth,

I wouldn't want this to be a blanket approach if it where ever
implemented.

If my ZODB is so big that it takes half an hour to rebuild, I would hate
it to be aborted just because the browser lost it's connection (ie IE
crashed ;-)

or running a big import. I don't need the browser to hang around for the
end result, I just want it to complete at some point. (ie kicking off
long running processes through xml-rpc, I don't want to keep the
connection open for the duration.)

Either you can programatically look at the state of the connection
(within the process and chose to kill it) or there was a console tool so
that you could see long running threads and kill them.

Rgds

Tim


On Wed, 2002-08-28 at 19:49, Chris Withers wrote:
 > 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 expensive SQL SELECT/JOIN? Why do we need this extra
 > programming overhead?
 >
 > As for the long running administrative tasks, I actually see the ability to
 > bugger off and leave them running as an extremely bad thing. Say I hit 'pack' on
 > a big fat ZODB. I then go somewhere else. How do I now tell when its done? The
 > only was would be to go and look at 'top' and guess which python thread is doing
 > the pack and wait till its CPU usage drops to zero. That's pretty ropey ;-)
 > For the same reason, I hate ZEO's pack's possibility of returning before a pack
 > is finished.
 >
 > If you do a pack, I really think you should wait for the browser to return. If
 > the browser times out, then use something like wget. If I hit 'stop', the pack
 > should abort.
 >
 > As a parting example, what happens if I accidentally start a pack? How can I
 > stop it? ;-)
 >
 > cheers,
 >
 > Chris
 >
 >
 > _______________________________________________
 > Zope-Dev maillist  -  Zope-Dev@zope.org
 > http://lists.zope.org/mailman/listinfo/zope-dev
 > **  No cross posts or HTML encoding!  **
 > (Related lists -
 >  http://lists.zope.org/mailman/listinfo/zope-announce
 >  http://lists.zope.org/mailman/listinfo/zope )