[
https://issues.apache.org/jira/browse/ARTEMIS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15636593#comment-15636593
]
ASF GitHub Bot commented on ARTEMIS-550:
----------------------------------------
Github user mattrpav commented on the issue:
https://github.com/apache/activemq-artemis/pull/875
@graben
re: Transacted: if the PostOffice is transacted by default, that's great.
The option in 5.x felt more like a "shore-up" to get to transacted. I don't see
a compelling reason to support non-transacted broker-side message movement. A
note in the migration guide would suffice.
re: Concurrency: I see this having value, and agree it should be a separate
JIRA/PR.
re: Selector/Filter: that's great that you have it on your radar. You
mentioned filter, so I feel obligated to clarify-- this selector is determined
by the _consumer_ using the standard JMS selector available in the API. The
broker then store these to properly filter messages if the consumer goes
offline. Does Artemis' filter support this behavior, or is filtering
broker-side configuration?
Thanks!
> Add support for virtual topic consumers
> ---------------------------------------
>
> Key: ARTEMIS-550
> URL: https://issues.apache.org/jira/browse/ARTEMIS-550
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: Broker
> Affects Versions: 1.3.0
> Reporter: Benjamin Graf
>
> Artemis should support virtual topic consumers as alternative to topic
> subscriptions as ActiveMQ itself does.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
