Robert Burrell Donkin ha scritto:
On Feb 8, 2008 10:33 AM, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
Danny Angus ha scritto:
Get it now?
No. What is the problem in redeploying all the processors every time you
need to redeploy one of them? You will have to stop the spoolmanager
thread anyway, so I don't see a big advantage in the big effort needed
to be able to redeploy a single processor (It would require much more
changes in our CoP, than full spoolmanager redeploy).
shoulnd't need to stop the master thread, just the worker for the
processor in question.
There is no "worker for a processor" concept right now. Threads are
started from the spoolmanager, they wait (blocking call) for a new
message in the spoolrepository and when a message is returned they look
at the state of the message and they run the mail through the associated
processor (if you use the default StateAwareProcessorList implementation).
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
