[Zope] Cancelling long processes in Zope

[Andreas Jung]

I think it is good practice to deal with long-running processes using a 
dedicated ZEO client and not to use a website for this. Especially because 
a long-running request allocates one thread. If you have four threads 
(default) and a user double or trible-clicks on the same link this will eat 
up all of your threads.

-aj

--On 19. August 2005 01:31:28 -0500 Ausum Studio <ausum_studio at hotmail.com> 
wrote:

> How do you stop a long process just triggered, i.e., by accident?  One of
> our apps allows our users to trigger long processes. The way we used to
> deal with them is to stream response lines so that the user has an idea
> of what's going on. Nonetheless, some processes aren't worth to watch, so
> they are simply logged and associated to a mail alert. That's fine so far.
>
> As processes can commit transactions regularly on demand, has anyone tried
> to deal with long processes by means of hacking the Zope threads machinery
> (or something like that), in order to achieve start, stop and resume
> commands? Most transactions don't need this, but unawared long procceses
> use to leak memory and CPU cycles, and they ought to be managed.
>
> Any experiences on this subject? Thanks in advance,
>
>
> Ausum
> _______________________________________________
> Zope maillist  -  Zope at zope.org
> http://mail.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists -
>  http://mail.zope.org/mailman/listinfo/zope-announce
>  http://mail.zope.org/mailman/listinfo/zope-dev )



-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 186 bytes
Desc: not available
Url : http://mail.zope.org/pipermail/zope/attachments/20050819/6e7f9112/attachment.bin