Return-Path: Delivered-To: apmail-activemq-users-archive@www.apache.org Received: (qmail 21125 invoked from network); 20 Apr 2007 15:15:54 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Apr 2007 15:15:54 -0000 Received: (qmail 48024 invoked by uid 500); 20 Apr 2007 15:16:00 -0000 Delivered-To: apmail-activemq-users-archive@activemq.apache.org Received: (qmail 47910 invoked by uid 500); 20 Apr 2007 15:15:59 -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 47901 invoked by uid 99); 20 Apr 2007 15:15:59 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 20 Apr 2007 08:15:59 -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; Fri, 20 Apr 2007 08:15:51 -0700 Received: from [72.21.53.38] (helo=jubjub.nabble.com) by talk.nabble.com with esmtp (Exim 4.50) id 1Heupe-0001du-SQ for users@activemq.apache.org; Fri, 20 Apr 2007 08:15:30 -0700 Message-ID: <10104315.post@talk.nabble.com> Date: Fri, 20 Apr 2007 08:15:30 -0700 (PDT) From: "dr.jeff" To: users@activemq.apache.org Subject: [camel] Comments on MINA coment MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Nabble-From: jlansing@systechnologies.com X-Virus-Checked: Checked by ClamAV on apache.org I was attracted to Camel by the existance of the MINA component, but I now see that it has some deficiencies. Very generally there can be 4 kinds of MINA endpoints: 1) acceptors ("server sockets", that accept connections) that initiatiate request/responses, 2) acceptors that wait for requests (eg, HTTP servers), 3) listeners (i.e., connection initiators) that initiatiate request/responses (eg. HTTP clients), and 4) listeners that that connect, then wait for requests, and then respond. It would be nice if Camel could provide a transparent easy-to-use way to plug and play with any of these four. -- View this message in context: http://www.nabble.com/-camel--Comments-on-MINA-coment-tf3618836s2354.html#a10104315 Sent from the ActiveMQ - User mailing list archive at Nabble.com.