Some useful reading links, for the concept in JMS terms/other implementations (which users might expect us to support/be close ot semantically). I'm not saying any of these approaches are exactly correct, but that the logical behaviour they support is similar.
http://activemq.apache.org/message-groups.html http://www.ibm.com/developerworks/websphere/library/techarticles/0602_currie/0602_currie.html http://forum.springsource.org/showthread.php?48798-Spring-2.5.1-JMS-1.1-and-distributed-jobs-implementation Marnie On Wed, Jun 29, 2011 at 10:33 AM, Marnie McCormack < [email protected]> wrote: > Message groups are typically used for items such as steps in a trade or a > workflow process, so that all parts of a group are processed in a single > transaction or not until all data required to process the action has > arrived. Queues are different as the data may be entirely unrelated. > Marnie > On Tue, Jun 28, 2011 at 4:10 PM, mick <[email protected]> wrote: > >> On Tue, 2011-06-28 at 15:51 +0100, Gordon Sim wrote: >> >> > >> > E.g. imagine the group relates to some real world object being >> > modelled >> > and each message contains describes an update >> >> >> To me that situation seems like it should be modeled as a queue. >> >> I think it would be very worthwhile in this discussion to figure out at >> what point we feel that a customer ought to opt for a queue rather than >> a message group. >> >> >> >> >> >> --------------------------------------------------------------------- >> Apache Qpid - AMQP Messaging Implementation >> Project: http://qpid.apache.org >> Use/Interact: mailto:[email protected] >> >> >
