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,

Zope maillist  -
**   No cross posts or HTML encoding!  **
(Related lists - )

Reply via email to