Return-Path: Delivered-To: apmail-activemq-dev-archive@www.apache.org Received: (qmail 16942 invoked from network); 2 May 2007 18:52:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 May 2007 18:52:29 -0000 Received: (qmail 92799 invoked by uid 500); 2 May 2007 18:52:35 -0000 Delivered-To: apmail-activemq-dev-archive@activemq.apache.org Received: (qmail 92771 invoked by uid 500); 2 May 2007 18:52:35 -0000 Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@activemq.apache.org Delivered-To: mailing list dev@activemq.apache.org Received: (qmail 92762 invoked by uid 99); 2 May 2007 18:52:35 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 May 2007 11:52:35 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of lists@nabble.com designates 72.21.53.35 as permitted sender) Received: from [72.21.53.35] (HELO talk.nabble.com) (72.21.53.35) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 May 2007 11:52:28 -0700 Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1HjJvs-00008u-Jp for dev@activemq.apache.org; Wed, 02 May 2007 11:52:08 -0700 Message-ID: <10292275.post@talk.nabble.com> Date: Wed, 2 May 2007 11:52:08 -0700 (PDT) From: northshorefiend To: dev@activemq.apache.org Subject: WebClient and multiple chat client MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: spam123@JamesAshepherd.com X-Virus-Checked: Checked by ClamAV on apache.org As many before me, I'm sure, I tried the activemq-web-demo chat client and found that you only get one working chat client per HttpSession. I'm new to ActiveMQ, but has anyone tried something like optionally having amq(.js) instances having a UID on birth and passing that to MessageListenerServlet, which uses a corresponding instance of WebClient stored in the HttpSession. Seems to me this would enable the MesssageListenerServlet to know which amq instance it was replying to, and each WebClient would acting on behalf of a single amq instance. I assume this behaviour may not be wanted by most users, but apart from that, am I missing any asynchronous consequences? If this is sensible I might try putting together a patch. -- View this message in context: http://www.nabble.com/WebClient-and-multiple-chat-client-tf3682481s2354.html#a10292275 Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.