[Design] (no subject)

[patrickdlogan at attbi.com]

<quote>Perhaps it would be prudent to look at 
how reliable messaging systems work (i.e., Java 
Messaging System)?</quote>

Not sure this belongs on the design list, vs. dev, but...

Very simply, a reliable message queue has some transactional device either in a
central location or at the end points or at some points in between.

The "transaction devices" are typically an embedded (often relational) database,
or just a file system.

Tuple spaces are the more flexible choice vs. a message queue. A high
performance message queue has network configuration options not found in the
tuple spaces I am aware of. Unless very high volume messages are required to be
routed among multiple subnets in selective ways, the more flexible choice is a
tuple space architecture.

Tuple spaces (or XML document spaces, going forward) are the 80% choice over
related technologies: databases (oltp), message queues, and workflows. Only in
the 20% corner cases would it make sense to go with a non-tuple space architecture.

-Patrick