cassandra-client-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Morton <>
Subject Re: Cassandra Perl interface
Date Wed, 01 Sep 2010 03:03:22 GMT

Seems a bit of overkill to pull C or C++ into the mix. The issues seem to be the best algorithm design
and being able to detect the ring membership correctly. Do not think it's  a problem than
cannot be solved inside python or any other language for that matter. 


On 01 Sep, 2010,at 02:21 PM, Dave Viner <> wrote:

I was thinking of something similar... but here's my real question about

Why not use the C or C++ bindings for cassandra's thrift implementation and
make a SWIG based module? Then, all the ugliness can reside in c/c++ and
swig-ing module is a fairly well-defined path.

I haven't actually tried to write any code to do it... more mental
gymnastics to consider it.

Any reason you didn't got the SWIG route?

Dave Viner

On Tue, Aug 31, 2010 at 7:17 PM, Chip Salzenberg <> wrote:

> > The purpose of this list is discussion pertaining to the development of
> > client APIs (think Pycassa, Hector, Pelops, Scromium, LazyBoy, etc).
> I'm working on a Cassandra interface for Perl that uses the C++ thrift
> bindings. (Perl is not the ideal language for protocol twiddling, and
> the thrift generated Perl code is very far from theoretical maximum
> performance.) Almost none of the protocol itself is implemented yet,
> but the C/Perl plumbing is under construction, and the module does
> actually build. Code is at

  • Unnamed multipart/alternative (inline, None, 0 bytes)
    • Unnamed multipart/related (inline, None, 0 bytes)
View raw message