Optimize session acked durable subs by using a shared durable queue.
--------------------------------------------------------------------

                 Key: APLO-20
                 URL: https://issues.apache.org/jira/browse/APLO-20
             Project: ActiveMQ Apollo
          Issue Type: New Feature
          Components: apollo-bdb, apollo-broker, apollo-cassandra, apollo-jdbm2
            Reporter: Hiram Chirino


Right now every durable sub gets assigned a new queue.  This is only needed to support out of order acking from the subscription.  If the consumer is doing in order acking like the JMS API forces, then you can get better performance by using a shared queue /w browsers but track ack positions using a simple map/index.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira