We have our own internal framework on top of protobufs, which is probably the
way I'm going for now.
Thanks,
-amol
-Original Message-
From: bbo...@gmail.com [mailto:bbo...@gmail.com]
Sent: Tuesday, August 17, 2010 2:31 PM
To: dev@cassandra.apache.org
Subject: Re: Adding protocol buffers
"Amol Deshpande" writes:
>
> Is that the right place to start ? Are there other parts of the code
> that are involved in implementing the client interface ?
just out of curiosity, which RPC implementation on top of protobuffers
are you planning on using?
-Bjørn
That would be the right model to follow, although I think you might
have an easier time maintaining a PB -> Thrift proxy in front of
Cassandra.
On Tue, Aug 17, 2010 at 2:49 PM, Amol Deshpande
wrote:
> For various reasons (existing codebase, clients running C#, etc.), we
> are considering implemen
For various reasons (existing codebase, clients running C#, etc.), we
are considering implementing a client interface that understands Google
protocol buffers.
>From browsing the source in trunk, it looks like the model to follow is
CassandraServer.java in org.apache.cassandra.avro
Is that the ri
+ 1 to all suggestions from Bjorn, but I'm sorry I can't devote time to it.
FWIW there's an old issue I once reported which tells part of the story. At
the time it was resolved as Won't Fix, but as Gary mentioned, time change
https://issues.apache.org/jira/browse/CASSANDRA-741 (Refactor for
testabi
Gary Dusbabek writes:
>
> I looked into doing this when I was first learning the code and had an
> experience simliar to yours. At the time there wasn't much interest
> in seeing it through to fruition, but maybe times have changed.
any lack of interest in solving these problems just means that
