Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 14625 invoked from network); 7 Mar 2007 17:18:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 7 Mar 2007 17:18:32 -0000 Received: (qmail 63740 invoked by uid 500); 7 Mar 2007 17:18:40 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 63722 invoked by uid 500); 7 Mar 2007 17:18:40 -0000 Mailing-List: contact users-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@activemq.apache.org Delivered-To: mailing list users@activemq.apache.org Received: (qmail 63707 invoked by uid 99); 7 Mar 2007 17:18:40 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Mar 2007 09:18:40 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of james.strachan@gmail.com designates 64.233.182.189 as permitted sender) Received: from [64.233.182.189] (HELO nf-out-0910.google.com) (64.233.182.189) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Mar 2007 09:18:28 -0800 Received: by nf-out-0910.google.com with SMTP id y38so256104nfb for ; Wed, 07 Mar 2007 09:18:06 -0800 (PST) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gZVlVWYIimIDb3kaurX/r3xC73nFt2zbwUx+vcydN1Ua2tsXPHhVlPVqADWoNhw8c6Kx+HMhMtK/q9wFp5PNcElzezG3YO/J1ncG5g5OIn3RXYo/nxoo+LWLNwQ4SKiAct5OvJ9Jv5M12vqpyOEENLzRPgtskf/UUHZYzicy/5M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=bp8koyqz988ST6c3OvcTorWnKNLmHzq7Wv2dNE/pQIlYyEVw5usE5fd2iyMXc3ire+eyksC5Xs9UZrKD6hQNts/xjoisCOFalMZZMCwiu6zcbksO1sMsx0tq2vyRwwIVmGR2h7fJVxiEf35z3lwTGTWanflpwSELfZt/OZj7Ls4= Received: by 10.78.179.12 with SMTP id b12mr1011240huf.1173287883490; Wed, 07 Mar 2007 09:18:03 -0800 (PST) Received: by 10.78.155.11 with HTTP; Wed, 7 Mar 2007 09:18:03 -0800 (PST) Message-ID: Date: Wed, 7 Mar 2007 17:18:03 +0000 From: "James Strachan" To: users@activemq.apache.org Subject: Re: Stomp: how to reply to a client? In-Reply-To: <45EEF180.8080907@wideopenwest.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <45EEF180.8080907@wideopenwest.com> X-Virus-Checked: Checked by ClamAV on apache.org On 3/7/07, Thomas Gagn=E9 wrote: > I'm probably confused... > > I have a client program that connects fine, and sends a message to > /queue/echo that I'd like to echo back to it. In this case it send > "Hello, world." > > I have a program that subscribes to /queue/echo and waits for frames to > arrive. When one arrives I want it to echo the frame's body back to the > client that sent it. It receives a MESSAGE with the body "Hello, > world." but I'm unsure how to reply back to the client. > > If 100 clients are all sending messages to /queue/echo, how are programs > supposed to respond back to the client that sent the message? So generally this involves replying to the 'reply-to' destination which is described here... http://stomp.codehaus.org/Stomp+JMS when sending a message to a queue, if you want a reply, set the reply-to header to point to the queue you will use to process replies. The one thing thats missing right now is an easy Stomp way to create temporary queues (in JMS-speak) for transient reply-to queues that last the duration of your client. For now just use a queue per client. --=20 James ------- http://radio.weblogs.com/0112098/