svn commit: r1439583 - /activemq/activemq-apollo/trunk/apollo-website/src/documentation/stomp-manual.md

[ch...@apache.org]

Author: chirino
Date: Mon Jan 28 19:13:02 2013
New Revision: 1439583

URL: http://svn.apache.org/viewvc?rev=1439583&view=rev
Log:
Fixes APLO-280: Clarification about message groups

Clarify message groups documentation a bit.

Modified:
    activemq/activemq-apollo/trunk/apollo-website/src/documentation/stomp-manual.md

Modified: activemq/activemq-apollo/trunk/apollo-website/src/documentation/stomp-manual.md
URL: http://svn.apache.org/viewvc/activemq/activemq-apollo/trunk/apollo-website/src/documentation/stomp-manual.md?rev=1439583&r1=1439582&r2=1439583&view=diff
==============================================================================
--- activemq/activemq-apollo/trunk/apollo-website/src/documentation/stomp-manual.md (original)
+++ activemq/activemq-apollo/trunk/apollo-website/src/documentation/stomp-manual.md Mon Jan 28 19:13:02 2013
@@ -559,9 +559,11 @@ Message Groups are an enhancement to the
 
 Message Groups are logically like a parallel Exclusive Consumer. Rather 
 than all messages going to a single consumer, the stomp `message_group` header
-is used to define which message group the message belongs to. The Message Group feature
-then ensures that all messages for the same message group will be sent to only 1 consumer 
-at time.
+is used to define which message group the message belongs to. The Message Group 
+feature then ensures that all messages for the same message group will be sent to 
+the currently assigned consumer for the group.  The assigned consumer consumer
+for a message group may change but not before all messages sent to the previous
+consumer are acked or if the consumer is disconnected.
 
 Another way of explaining Message Groups is that it provides sticky load balancing 
 of messages across consumers; where the message group value is kinda like a HTTP