[
https://issues.apache.org/jira/browse/ARTEMIS-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15814941#comment-15814941
]
ASF GitHub Bot commented on ARTEMIS-562:
----------------------------------------
GitHub user gaohoward opened a pull request:
https://github.com/apache/activemq-artemis/pull/955
ARTEMIS-562 Use 'to' field if sender target is null
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gaohoward/activemq-artemis master_562
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/activemq-artemis/pull/955.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #955
----
commit e2a1a4dbb780b82810d6b9f116c9f6a7b4d2c810
Author: Howard Gao <[email protected]>
Date: 2017-01-10T12:51:42Z
ARTEMIS-562 Use 'to' field if sender target is null
----
> Use 'to' field if sender target is null
> ---------------------------------------
>
> Key: ARTEMIS-562
> URL: https://issues.apache.org/jira/browse/ARTEMIS-562
> Project: ActiveMQ Artemis
> Issue Type: New Feature
> Components: AMQP, Broker
> Affects Versions: 1.3.0
> Reporter: Gordon Sim
> Assignee: Howard Gao
> Attachments: anonymous-relay.patch, anonymous_sender.py
>
>
> ActiveMQ5 (and other AMQP brokers) support creating a sender with a null
> target, and then identifying the destination of each messages via the 'to'
> field. This is very useful in some request-response cases, as it avoids the
> 'service' having to create and manage senders for every reply-to address.
> Indeed the qpid-proton request-response examples rely on this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
