Return-Path: X-Original-To: apmail-activemq-users-archive@www.apache.org Delivered-To: apmail-activemq-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 90F6D74B for ; Mon, 20 Aug 2012 21:58:10 +0000 (UTC) Received: (qmail 56589 invoked by uid 500); 20 Aug 2012 21:58:10 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 56507 invoked by uid 500); 20 Aug 2012 21:58:10 -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 56495 invoked by uid 99); 20 Aug 2012 21:58:10 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Aug 2012 21:58:10 +0000 X-ASF-Spam-Status: No, hits=2.0 required=5.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: 216.139.250.139 is neither permitted nor denied by domain of zackhasit@gmail.com) Received: from [216.139.250.139] (HELO joe.nabble.com) (216.139.250.139) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Aug 2012 21:58:04 +0000 Received: from [192.168.236.139] (helo=joe.nabble.com) by joe.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1T3Zyi-000372-CE for users@activemq.apache.org; Mon, 20 Aug 2012 14:57:44 -0700 Date: Mon, 20 Aug 2012 14:57:44 -0700 (PDT) From: zackhasit To: users@activemq.apache.org Message-ID: <1345499864367-4655332.post@n4.nabble.com> In-Reply-To: References: <1345480110863-4655304.post@n4.nabble.com> <1345486615667-4655325.post@n4.nabble.com> Subject: Re: Implementing Request Response mechanism MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Thanks a lot for the code. I looked at it but if you can provide some comments it might help as I am only familiar with whats at http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html and not inner workings. But first question that comes to mind is if HTTP is right protocol. For regular communication (with one broker) does it use same HTTP protocol or its something more light weight (openwire / stomp )? Shoudl we use that ? (Maybe I dont understand what you are doing and thats the confusion...) Secondly, is this only way to communicate with multiple brokers. I looked at the code here (http://activemq.apache.org/how-should-i-implement-request-response-with-jms.html) Based on this code cant I just set up combine client and server code in one process and run it as : public static void main(String[] args) { new Server(); new client(); } In doing so I can have different values for variable "messageBrokerUrl = "tcp://localhost:61616";" for client and server. Such that when client sends requests it sends to one broker connection in client class defined in code and server class implements onMessage() function to receive from different connection ? Is something like that possible (more standard implementation) ? >>messaging service/broker as a sort of rate-control/throttling mechanism between client-server? Yes (and load balancing where 3 consumers for 1 producer....). -- View this message in context: http://activemq.2283324.n4.nabble.com/Implementing-Request-Response-mechanism-tp4655304p4655332.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.