Return-Path: X-Original-To: apmail-camel-users-archive@www.apache.org Delivered-To: apmail-camel-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 5F3A39C8F for ; Tue, 10 Apr 2012 23:43:51 +0000 (UTC) Received: (qmail 96303 invoked by uid 500); 10 Apr 2012 23:43:50 -0000 Delivered-To: apmail-camel-users-archive@camel.apache.org Received: (qmail 96269 invoked by uid 500); 10 Apr 2012 23:43:50 -0000 Mailing-List: contact users-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@camel.apache.org Delivered-To: mailing list users@camel.apache.org Received: (qmail 96261 invoked by uid 99); 10 Apr 2012 23:43:50 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Apr 2012 23:43:50 +0000 X-ASF-Spam-Status: No, hits=2.3 required=5.0 tests=SPF_SOFTFAIL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: softfail (athena.apache.org: transitioning domain of v_cheruvu@hotmail.com does not designate 216.139.236.26 as permitted sender) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Apr 2012 23:43:45 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1SHkib-0006q7-Cn for users@camel.apache.org; Tue, 10 Apr 2012 16:43:25 -0700 Date: Tue, 10 Apr 2012 16:43:25 -0700 (PDT) From: vcheruvu To: users@camel.apache.org Message-ID: <1334101405388-5631446.post@n5.nabble.com> In-Reply-To: <9B2891F2-1690-4177-AC45-FFB328B74705@gmail.com> References: <4CEBC462.3080207@navicon.dk> <1326444286227-5142063.post@n5.nabble.com> <1334040017637-5629124.post@n5.nabble.com> <9B2891F2-1690-4177-AC45-FFB328B74705@gmail.com> Subject: Re: tcp socket client consumer endpoint? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi Chad, Currently, I have to implement a tcp client that connects to a remote host. The following things takes place between client and remote host 1. Once connected to remote host, client send login message with a custom message format converted into bytes over wire. Remote host will send sucessfull login code to client. 2. Once login is successfull, TCP client send another message that defines our interest to get data from remote host as asynchronous mode. The remote host will understand our message and publishes data to our socket session. 3. While client is connected, Remote host will send ping to Client for heartbeat check. Client must respond to the heartbeat for remote host within a time period, this is to ensure that remote host doesn't think that client is down otherwise socket session is closed after 3 tries. I am trying to see if above is possible with camel-mina2 with custom processors/handlers for sending/receiving messages to/from remote host. Kind regards, -Vid- -- View this message in context: http://camel.465427.n5.nabble.com/tcp-socket-client-consumer-endpoint-tp3276804p5631446.html Sent from the Camel - Users mailing list archive at Nabble.com.