Return-Path: X-Original-To: apmail-kafka-dev-archive@www.apache.org Delivered-To: apmail-kafka-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7EE5018B89 for ; Wed, 6 Jan 2016 05:31:23 +0000 (UTC) Received: (qmail 40399 invoked by uid 500); 6 Jan 2016 05:31:23 -0000 Delivered-To: apmail-kafka-dev-archive@kafka.apache.org Received: (qmail 40288 invoked by uid 500); 6 Jan 2016 05:31:23 -0000 Mailing-List: contact dev-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list dev@kafka.apache.org Delivered-To: moderator for dev@kafka.apache.org Received: (qmail 32003 invoked by uid 99); 6 Jan 2016 05:22:59 -0000 X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 3.001 X-Spam-Level: *** X-Spam-Status: No, score=3.001 tagged_above=-999 required=6.31 tests=[HTML_MESSAGE=3, URIBL_BLOCKED=0.001] autolearn=disabled From: To: "'Gwen Shapira'" , , "'Prakash M N'" References: <003a01d14793$7011e2c0$5035a840$@com> In-Reply-To: Subject: RE: Reg. Kafka - Socket Communication from external system Date: Wed, 6 Jan 2016 10:52:36 +0530 Message-ID: <000501d14842$45e43480$d1ac9d80$@com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0006_01D14870.5F9C7080" X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: AdFH0AYBXMQ3lZpvRCKzn2FTSAgkLgAcbB2g Content-Language: en-us X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ns4.tecz.com X-AntiAbuse: Original Domain - kafka.apache.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - trinitymobility.com X-Get-Message-Sender-Via: ns4.tecz.com: authenticated_id: basavaraj@trinitymobility.com X-Authenticated-Sender: ns4.tecz.com: basavaraj@trinitymobility.com ------=_NextPart_000_0006_01D14870.5F9C7080 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi Gwen, =20 Thanks for your reply. =20 Our GPS device support TCP IP Socket communication with IP and Port. = Kindly suggest KAKFA supports directly or do we need to write service = layer for interface with KAFKA. =20 Thanks & Regards, Basavaraj =20 =20 =20 From: Gwen Shapira [mailto:gwen@confluent.io]=20 Sent: Tuesday, January 05, 2016 9:14 To: dev@kafka.apache.org Cc: basavaraj@trinitymobility.com Subject: Re: Reg. Kafka - Socket Communication from external system =20 Kafka requires a specific protocol and it is unlikely that GPS devices = will support this protocol out of the box. =20 The usual solution is to create a service that accepts GPS packets using = the protocol that GPS devices support, converts it to Kafka records and = produce them to a Kafka broker. =20 Gwen =20 On Tue, Jan 5, 2016 at 12:31 AM, Prakash M N = wrote: Hi, Please let us know whether KAFKA will support socket based communication with external GPS device. GPS Device will send GPS packet to the KAFKA = IP and Port. Thanks in Advance Thanks & Regards, Prakash MN =20 ------=_NextPart_000_0006_01D14870.5F9C7080--