>
> 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.
>
> Aaron
Here's my re
> Dave Viner writes:
>
> 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.
That sounds like a reasonable way to make Thrift, generally, faster on
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. Aaron On 01 Sep, 2010,at 02:21 PM, D
I was thinking of something similar... but here's my real question about
it...
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 tr
> 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 thri
