BTW one idea I had for making this kinda stuff easy to use on stomp was to add a CONNECT header something like
CONNECT auto-reply-to: true And that would under the covers, create a temporary destination for the client, subscribe to it, then append the reply-to header to each SEND so that services can easily reply to them. It then saves the stomp client with having to deal with the detail On 3/7/07, James Strachan <[EMAIL PROTECTED]> wrote:
On 3/7/07, Thomas Gagné <[EMAIL PROTECTED]> wrote: > As soon as I saw the "reply-to" header (a few minutes ago) I started > suspecting that each client would use two queues, one for sending > requests to and another for receiving replies on. I was looking around > for ways to create unique queues and though perhaps I can use the > connection information I get back from CONNECT to build a transient > queue name. Sure, that'd work. We'll add some kinda temporary-queue mechanism at some point. > Am I right in thinking then that a client might receive messages on both > queues? So each client would subscribe to just its own queues. Then 'services' would all consume on the service queue with messages load balanced across the services. -- James ------- http://radio.weblogs.com/0112098/
-- James ------- http://radio.weblogs.com/0112098/
