David Pratt wrote:
really interesting.I think it would be a really good thing to see fire
and forget with a process you create as a series of steps that can also
be queued in one or more queues.
Well, I think ZAsync would be great for building and managing the
queues, with Stepper steps
Ron Bickers wrote:
I have no idea. Maybe it'll do what you want, but I don't understand what it
really does just from the description. The work I needed to do was external
to Zope anyway (reading data from a MySQL database, building PDFs with
Reportlab, sending email), so it's actually
Hi David,
Just a note in passing to say that what you're really after in this case
is Gary Poster's ZASync. Gary's talked to me about getting Stepper
(which is basically batch processing triggered via cron using a ZEO
connection) to do the work of processing ZAsync's queue, which would be
On Fri September 23 2005 04:31 pm, Chris Withers wrote:
Ron Bickers wrote:
I have no idea. Maybe it'll do what you want, but I don't understand
what it really does just from the description. The work I needed to do
was external to Zope anyway (reading data from a MySQL database,
Hi Chris. I downloaded ZASync and did a bit of reading and comparing
between your Stepper product as well. ZASync at present relies on an
older version of Twisted which is now I think into the 2 series so
maybe later the products will come together this way. I think Stepper
is really
On Tue September 13 2005 02:52 pm, David Pratt wrote:
Hi. I have a workflow that is triggered by a file upload and the
processing of the file can be minutes of processing depending upon the
size of the file uploaded. I am concerned about number of threads
available to serve zope so I believe
Hi Ron. Many thanks for your reply. This is also a long running
document processing challenge, there can be 100's (or even thousands)
of records which is why the time problem. The code it uses in my tool
in the CMF. How is it that you send a signal to the long running
process? Is the long
On Tue September 13 2005 08:16 pm, David Pratt wrote:
How is it that you send a signal to the long running
process?
The long-running process writes a pid file and waits for a SIGUSR1 signal
(using Python's signal module). A small External Method, called when the
user submits the form, reads
Hi Ron. I found the following trying to follow up a bit on what you
have suggested. I believe it is similar to what you are doing from your
explanation. It may be out of date. I have not attempted to
daemonize a process to date so it would be great if you could look at
this and comment
