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
- Original Message -
From: Dieter Maurer [EMAIL PROTECTED]
(...)
I submitted a patch to the Zope collector but I had removed
one bit of black magic too much -- and other products broke that
were dependent on this magic.
My patch which were already integrated into the Zope
Is this a kafkanian situation? Are really core developers asking the
community to kick a used Zope's feature, saying it's because it's hard to
maintain it, and simultaneously to say it's code 'unmaintained and untouched
since ages'? Folks, you didn't need to ask for the aproval of people who
To me it depends on how much time ZClasses are going to last. If ZClasses
will stay for the next two years, then it's fine for us, as we probably will
persuade ourselves to rewrite all of our stuff in ZopeX3, and not in
Zope2.X
Jim, bear in mind that people that will agree to its deprecation
