> On Wed, 2002-08-28 at 07:49, Chris Withers wrote:
> > I'd like to see the REQUEST be flat plain aborted when someone hits the > > stop button or the connection dies. Thats probably impossible if there is an HTTP proxy between your browser and zope. > > 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 ;-) Yes, all good storages use zLOG to report that they are finished packing. ;-) On Wednesday 28 Aug 2002 2:47 pm, Chris McDonough wrote: > Do you have any implementation suggestions? On posix there may be some SIGINT-based options, which Im sure would expose many other weaknesses. On Win32, Im fairly sure we are out of luck for interruption without RESPONSE.isClientConnected() _______________________________________________ Zope-Dev maillist - [EMAIL PROTECTED] 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 )
