----- Original Message -----
From: "David Doucette" <[EMAIL PROTECTED]>
> From [EMAIL PROTECTED]
> > No docs to speak of. As it tries messages, if it fails it puts it back
in
> > the queue, incrementing a counter and recording the next time it should
> > attempt (based on the conf file). So if the server is restarted, it
will
> > remember where it was.
> So the queue exists in memory and on disk?
Nothing exists in memory.
> Very cool. As I think more about this, maybe it should be even more
> general purpose -- not only handling failure, but also success (or a
> separate one for each case). This way actions can be taken as the result
> of a successful delivery, not just as the result of a failed delivery.
> Again, I'm new to James, so maybe there is already some sort of
> mechanism to cause an action to happen upon success?
Messages for delivery just get consumed (success or failure). I like the
idea of another processor for successes, not that most people would use it
(at least not today).
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
