missing edit-log entry for this revision
converted to 1.6 markup
|Deletions are marked like this.||Additions are marked like this.|
|Line 9:||Line 9:|
|See Also: ["JamesV3/Plans"].||See Also: [[JamesV3/Plans]].|
Proposals and work plans for the James v3 Messsage Spool
The current proposal is to change the message spool to follow more of a basic put/get model, similar to that in util.concurrent queuing or T-spaces/JavaSpaces.
A message spool implementation could use a message store for persistence, but it would not be a message store.
A lightweight Mail object containing a reference to the Message will probably be part of the interface.
See Also: JamesV3/Plans.