That is a good point, really the platforms are all we need (C, JVM, .Net). -Jay
On Fri, Sep 9, 2011 at 5:47 AM, Chris Burroughs <[email protected]>wrote: > On 09/07/2011 12:21 PM, Jun Rao wrote: > > The approach that KAFKA-85 took is to re-write all the logic in our fat > > client (both the producer and the consumer) in C#. This means that a lot > of > > code has to be re-written and maintained and it's a lot of work if every > > language does the same thing. > > > > Would we really need to maintain code in every language, or just the > platforms: C, JVM, and .NET? > > > There are 2 other approaches that some Apache projects have used to > support > > different language binding. The first one is to use an RPC code generator > to > > directly expose the api to other languages. For example, Cassandra uses > > Thrift to define the client API and let Thrift generate language specific > > client code to talk to server. > > I agree that this isn't really the problem. One of the attractions of > Kafka is that it isn't wedded to a particular ser/deser library. >
