Questions: Next Receiver Functionality

["Flores, Paul A." <PA...@SAIC.COM>]

Hi,


Working at a client site and have run into an interesting question.


The current implementation plan is to use a unique "reply to" address (queue) to handle synchronous request reply. At this point we have a local broker so we have a single connection with a single session.


We are also planning to use the "next_receiver" functionality so we can "loop" through various queues to dispatch message contents to related processes.


Questions are:


Could "next_receiver" conceivably end up reading from a unique "reply to" queue?


If so does that mean we should use a different session (senders and receivers) for synchronous processing?


Thanks for comments and insights.


Paul


________________________________

This communication (including any attachments) may contain information that is proprietary, confidential or exempt from disclosure. If you are not the intended recipient, please note that further dissemination, distribution, use or copying of this communication is strictly prohibited. Anyone who received this message in error should notify the sender immediately by telephone or by return email and delete it from his or her computer.

Re: Questions: Next Receiver Functionality

["Flores, Paul A." <PA...@SAIC.COM>]

Gordon thanks for the quick response.

Looks like we are going to need to manage multiple sessions; one specific to asynchronous processing and another for synchronous.  Plan will be to utilize "next_receiver" for asynchronous processing and create unique senders and receivers for synchronous processing in the synchronous session.
________________________________________
From: Gordon Sim <gs...@redhat.com>
Sent: Thursday, September 1, 2016 11:13 AM
To: users@qpid.apache.org
Subject: Re: Questions: Next Receiver Functionality

On 01/09/16 17:52, Flores, Paul A. wrote:
> Hi,
>
>
> Working at a client site and have run into an interesting question.
>
>
> The current implementation plan is to use a unique "reply to" address (queue) to handle synchronous request reply. At this point we have a local broker so we have a single connection with a single session.
>
>
> We are also planning to use the "next_receiver" functionality so we can "loop" through various queues to dispatch message contents to related processes.
>
>
> Questions are:
>
>
> Could "next_receiver" conceivably end up reading from a unique "reply to" queue?
>
>
> If so does that mean we should use a different session (senders and receivers) for synchronous processing?

next_receiver will return any receiver for which there is a message
waiting to be read


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org


________________________________

This communication (including any attachments) may contain information that is proprietary, confidential or exempt from disclosure. If you are not the intended recipient, please note that further dissemination, distribution, use or copying of this communication is strictly prohibited. Anyone who received this message in error should notify the sender immediately by telephone or by return email and delete it from his or her computer.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org

Re: Questions: Next Receiver Functionality

[Gordon Sim <gs...@redhat.com>]

On 01/09/16 17:52, Flores, Paul A. wrote:
> Hi,
>
>
> Working at a client site and have run into an interesting question.
>
>
> The current implementation plan is to use a unique "reply to" address (queue) to handle synchronous request reply. At this point we have a local broker so we have a single connection with a single session.
>
>
> We are also planning to use the "next_receiver" functionality so we can "loop" through various queues to dispatch message contents to related processes.
>
>
> Questions are:
>
>
> Could "next_receiver" conceivably end up reading from a unique "reply to" queue?
>
>
> If so does that mean we should use a different session (senders and receivers) for synchronous processing?

next_receiver will return any receiver for which there is a message 
waiting to be read


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org
For additional commands, e-mail: users-help@qpid.apache.org