Return-Path: 
 <camel-user-return-4191-apmail-activemq-camel-user-archive=activemq.apache.org@activemq.apache.org>
Delivered-To: apmail-activemq-camel-user-archive@locus.apache.org
Received: (qmail 64626 invoked from network); 11 Nov 2008 01:29:11 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 11 Nov 2008 01:29:11 -0000
Received: (qmail 87559 invoked by uid 500); 11 Nov 2008 01:29:18 -0000
Delivered-To: apmail-activemq-camel-user-archive@activemq.apache.org
Received: (qmail 87545 invoked by uid 500); 11 Nov 2008 01:29:18 -0000
Mailing-List: contact camel-user-help@activemq.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:camel-user-help@activemq.apache.org>
List-Unsubscribe: <mailto:camel-user-unsubscribe@activemq.apache.org>
List-Post: <mailto:camel-user@activemq.apache.org>
List-Id: <camel-user.activemq.apache.org>
Reply-To: camel-user@activemq.apache.org
Delivered-To: mailing list camel-user@activemq.apache.org
Received: (qmail 87534 invoked by uid 99); 11 Nov 2008 01:29:18 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 10 Nov 2008 17:29:18 -0800
X-ASF-Spam-Status: No, hits=2.6 required=10.0
	tests=DNS_FROM_OPENWHOIS,SPF_HELO_PASS,SPF_PASS,WHOIS_MYPRIVREG
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Received: from [216.139.236.158] (HELO kuber.nabble.com) (216.139.236.158)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 11 Nov 2008 01:27:57 +0000
Received: from isper.nabble.com ([192.168.236.156])
	by kuber.nabble.com with esmtp (Exim 4.63)
	(envelope-from <lists@nabble.com>)
	id 1Kzi3b-0000IX-Ag
	for camel-user@activemq.apache.org; Mon, 10 Nov 2008 17:28:39 -0800
Message-ID: <20431804.post@talk.nabble.com>
Date: Mon, 10 Nov 2008 17:28:39 -0800 (PST)
From: Jeff V <Jeff.Vienneau@Ultra-UEMS.com>
To: camel-user@activemq.apache.org
Subject: Can mina::tcp do asyncronous bidirectional messages?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Nabble-From: Jeff.Vienneau@Ultra-UEMS.com
X-Virus-Checked: Checked by ClamAV on apache.org


The service I am connecting to is a TCP server mode socket that simultaneusly
supports two modes of communication: 

1) Request / Response 
AMQ: <Request><ParameterQuery param="temperature" /></Request> 
DEV:  <Response><QueryResult param="temperature" value="22.5"/></Response> 

AND

2) unsolicited events 
DEV:  <Event><ParameterAlarm param="temperature" value="30.1" desc="high
temperature"/></Event> 

In my slightly contrived example, AMQ is the ActiveMQ generating out bound
requests and DEV represents a device connected to the TCP port responding to
requests and also is generating event messages. 

I would like two way async communications such that my update messages can
flow into AMQ and be routed to topic subscribers, logs, persistent storage,
email etc.. 

I do not need the request response to a camel exchange, I will handle that
at a higher level.

Can I do this with the camel-mina component? If so, how?

If not, what would the best way to proceed be? 
Perhaps, a bean that is subscribing to messages for outbound and a TCP
listener thread for inbound?

Any help is much appreciated!!
-- 
View this message in context: http://www.nabble.com/Can-mina%3A%3Atcp-do-asyncronous-bidirectional-messages--tp20431804s22882p20431804.html
Sent from the Camel - Users mailing list archive at Nabble.com.