RE: CQL3 Frame Length

2013-01-21 Thread Pierre Chalamet
l, it's v1 - there are still 0x7E more versions to get it better. - Pierre From: Theo Hultberg [mailto:t...@iconara.net] Sent: Saturday, January 19, 2013 6:33 PM To: user@cassandra.apache.org Subject: Re: CQL3 Frame Length Hi, Another reason for keeping the frame length in the header is that new

Re: CQL3 Frame Length

2013-01-19 Thread Theo Hultberg
Hi, Another reason for keeping the frame length in the header is that newer versions can add fields to frames without older clients breaking. For example a minor release can add some more content to an existing frame without older clients breaking. If clients didn't know the full frame length (and

Re: CQL3 Frame Length

2013-01-08 Thread Ben Hood
Hey Sylvain, Thanks for explaining the rationale. When you look at from the perspective of the use cases you mention, it makes sense to be able to supply the reader with the frame size up front. I've opted to go for serializing the frame into a buffer. Although this could materialize an arbitrari

Re: CQL3 Frame Length

2013-01-08 Thread Sylvain Lebresne
Mostly this is because having the frame length is convenient to have in practice. Without pretending that there is only one way to write a server, it is common to separate the phase "read a frame from the network" from the phase "decode the frame" which is often simpler if you can read the frame u