> > Possibly help for distribution, but I really want the spooler to be
> > that mechanism, and we cannot tie its interface to Avalon.
> I don't really follow the above with respect to the "spooler"
> and "mechamism" - sorry!
The services and pipleline are connected by a spooler. The spooler
interface needs to be portable. If the implementation of the spooler allows
clustering, which is a goal, then we can locate different parts of James on
different JVMs, connected via the spooler. That will probably not be
sufficient, since they will also want to be able to access MailetContext
information, repositories, etc., which we may want to share, but it is a key
piece.
JMS is one technology that we *might* be able to use to implement
distribution. Alternatively, one might use a shared database, a tuple-space
service, or ...
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
