On Thu, 2011-03-31 at 13:56 +0200, Bjorn Borud wrote:
> > (Hopefully )for the next version, we'll replace Thrift with a
> > dedicated protocol, one that eliminates the Thrift dependency, and
> > more importantly, implements streaming. This should be transparent
> > to applications for the most
Eric Evans writes:
> (Hopefully )for the next version, we'll replace Thrift with a dedicated
> protocol, one that eliminates the Thrift dependency, and more
> importantly, implements streaming. This should be transparent to
> applications for the most part though.
pardon my ignorance, is there
On Sun, 20 Mar 2011 19:56:39 -0500 Eric Evans wrote:
EE> (Hopefully )for the next version, we'll replace Thrift with a dedicated
EE> protocol, one that eliminates the Thrift dependency, and more
EE> importantly, implements streaming. This should be transparent to
EE> applications for the most p
On Sun, 2011-03-20 at 22:11 +, Courtney Robinson wrote:
> I've been looking at the Java and Python drivers and they are both
> using Thrift. I thought the idea was to get rid of thrift/avro?
The idea is to create an alternative to the tightly-coupled
object-oriented RPC interface.
This initia
I've been looking at the Java and Python drivers and they are both using
Thrift. I thought the idea was to get rid of thrift/avro?
The two implemented (however partial) drivers seem to have similar naming
conventions for class and methods.
Has it been agreed to try and do this? I reckon it'd be
