[ https://issues.apache.org/jira/browse/PROTON-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13790364#comment-13790364 ]
Ted Ross edited comment on PROTON-439 at 10/9/13 2:00 PM: ---------------------------------------------------------- Here's a proposed algorithm assuming Ken's suggested "put-request" API: {noformat} put_request(msg): conn = lookup_or_create_connection_for_address(msg.address) if a reply receiver-link exists for conn rlink = existing_reply_link else rlink = create_new_receiver(conn, dynamic=true) subscribe to rlink msg.reply_to = rlink.remote_source enqueue(msg) {noformat} was (Author: tedross): Here's a proposed algorithm assuming Ken's suggested "put-request" API: <noformat> put_request(msg): conn = lookup_or_create_connection_for_address(msg.address) if a reply receiver-link exists for conn rlink = existing_reply_link else rlink = create_new_receiver(conn, dynamic=true) subscribe to rlink msg.reply_to = rlink.remote_source enqueue(msg) <noformat> > Support for dynamic reply-to address in Messenger > ------------------------------------------------- > > Key: PROTON-439 > URL: https://issues.apache.org/jira/browse/PROTON-439 > Project: Qpid Proton > Issue Type: New Feature > Components: proton-c > Affects Versions: 0.5 > Reporter: Ted Ross > > Messenger has no support for creating dynamic receivers for reply-to > addresses. Please refer to the following email thread for prior discussion > on the topic. > http://qpid.2158936.n2.nabble.com/Proton-Messenger-and-the-Request-Response-pattern-tp7586653.html -- This message was sent by Atlassian JIRA (v6.1#6144)