thanks for the high level description of the format, I'll see if I can make
a stab at implementing support for custom types now.
and maybe I should take all of the reverse engineering I've done of the
type encoding and decoding and send a pull request for the protocol spec,
or write an appendix.
Please do. I too am working at a driver implementation and would be
delighted to be spared the research.
On Feb 25, 2014 11:29 AM, Theo Hultberg t...@iconara.net wrote:
thanks for the high level description of the format, I'll see if I can
make a stab at implementing support for custom types
(I posted this on the client-dev list the other day, but that list seems
dead so I'm cross posting, sorry if it's the wrong thing to do)
Hi,
Is there any documentation on how CQL clients should handle the new user
defined types coming in 2.1? There's nothing in the protocol specification
on how
On Mon, Feb 24, 2014 at 7:52 PM, Theo Hultberg t...@iconara.net wrote:
(I posted this on the client-dev list the other day, but that list seems
dead so I'm cross posting, sorry if it's the wrong thing to do)
I didn't even realize there was a list for driver implementors - is
this used at all?
There hasn't been any activity (apart from my question) since december, and
only sporadic activity before that, so I think it's essentially dead.
http://www.mail-archive.com/client-dev@cassandra.apache.org/
T#
On Mon, Feb 24, 2014 at 10:34 PM, Ben Hood 0x6e6...@gmail.com wrote:
On Mon, Feb
