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 a good idea if that
was the case because then no matter which language driver you're using you
you can easily use any other driver/language since the methods/function
names would be the same or similar and would mean its easier to
develop different components in different languages since you won't have to
learn a new API for the various drivers... or at least you'd have an easier
time
I think this would address one of the problems now with different clients
providing their own API which vary widely across the board.
Maybe using UML to indicate which methods/functions each driver needs to
provide. I generated some UML from the Java driver and from that result
the only issue I can think of in languages like PHP that don't have a
Collections API data return types would have to be appropriate to the
language.
Thoughts?
