On 02/29/2012 03:21 PM, Kim van der Riet wrote:
The current async store's use of DataTokens corresponds with the second proposal, ie one DataToken corresponds to a single enqueue. Switching to a MessageToken will require (at least from the current async store point-of-view) the maintenance of a map of queues on which this message is stored and then hang its enqueue-specific data there... This represents a departure from the current mechanism and an increase in complexity to the store.
To be clear I am not suggesting that the same MessageToken is used for enqueues on multiple different queues.
In any case though, you must already be maintaining that map since the current store interface only has a PersistableMessage with its persistence ID as the context to an enqueue (and dequeue) along with the PersistableQueue. Or am I misunderstanding?
--------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
