Mailing-List: contact kafka-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: kafka-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of chris.burroughs@gmail.com
 designates 209.85.216.47 as permitted sender)
Message-ID: <4EDA7348.90607@gmail.com>
Date: Sat, 03 Dec 2011 14:06:48 -0500
From: Chris Burroughs <chris.burroughs@gmail.com>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
 rv:1.9.2.23) Gecko/20110922 Thunderbird/3.1.15
MIME-Version: 1.0
To: kafka-dev@incubator.apache.org
CC: David Ormsbee <dave@datadoghq.com>
Subject: Re: Guide to Writing a Client for Kafka
References: 
 <CALStshbz100urVRnk5BgPwypGQQKj0_3iXZJM1a2iS0_iCK3zw@mail.gmail.com>
In-Reply-To: 
 <CALStshbz100urVRnk5BgPwypGQQKj0_3iXZJM1a2iS0_iCK3zw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Great work!

Having a solid doc/spec for the wire protocol would also likely decrease
the need to have as many clients in-tree.  I think at this point that
would be a good thing.

On 11/23/2011 06:32 PM, David Ormsbee wrote:
> Hi folks,
> 
> Inspired by the Wire Format wiki entry, I recently created a draft of
> "Writing a Client for Kafka":
> 
>   http://readthedocs.org/docs/brod/en/latest/spec.html
> 
> I tried to make it the document that I wish we had at Datadog when we
> were total Kafka newbies writing client code. It's still very rough
> and littered with "FIXME" notes where I've written things from my
> understanding without verifying them with tests. I should be filling
> all these gaps in soon, as we're planning to add a lot of
> functionality to our Python client in the coming weeks.
> 
> Comments and corrections would be greatly appreciated. :-)
> 
> Thank you very much to the Kafka devs. We've been using Kafka a great
> deal at Datadog, we're extremely happy with it, and we're looking
> forward to contributing in our own way. We'll make an announcement as
> soon as we feel our Python client is ready for community use.
> 
> Take care.
> 
> Dave