[
https://issues.apache.org/jira/browse/ARTEMIS-550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15637041#comment-15637041
]
ASF GitHub Bot commented on ARTEMIS-550:
----------------------------------------
Github user rlodge commented on the issue:
https://github.com/apache/activemq-artemis/pull/875
@mtaylor What I'm hearing is that basically, following changes in 780, a
client would be able to send to an address "RecordUpdateNotifications", other
clients could subscribe to
"RecordUpdateNotifications::SystemARecordUpdateNotifications" and it would act
essentially like virtual topics do now; all "RecordUpdateNotifications::*"
subscriptions would read from queues coming from the single address?
If so, do OpenWire clients need to use a specific queue / address naming
scheme, or would it happen automatically somehow (and could it be mapped from
the VirtualTopic.* naming scheme)? It's not a terribly large problem for us to
go through and change our queues from VirtualTopic.* to a slightly different
naming scheme, though we'd rather change nothing about the clients; it would be
more difficult to somehow change the API's we were calling...
> 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)
