[
https://issues.apache.org/jira/browse/CASSANDRA-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410599#comment-13410599
]
paul cannon commented on CASSANDRA-2478:
----------------------------------------
bq. 3. we will be nice and have server understand old protocol version for at
least 1 or 2 major C* version after we've changed them.
Ok, a guarantee like this, plus the reporting of supported protocol versions in
OPTIONS, alleviates most of my concern.
bq. New queries capabalities will not imply a change in the protocol for
instance. Typically, I don't know that libpq changes all the time or lacks
hundreds of features.
It's interesting that you bring that up, because libpq uses 32 bits for its
versioning. 16 bits for a major version, and 16 for a minor. And no, it doesn't
change much. :)
I see your point, though, that limiting the space to 7 bits should be a strong
discouragement against making changes, which ought to result in a more stable
protocol. I don't quite share the optimism of how well it will serve us, but I
do at least understand, and I guess having the option of "version==127 -> use
additional bytes for version" in the future is good enough.
> Custom CQL protocol/transport
> -----------------------------
>
> Key: CASSANDRA-2478
> URL: https://issues.apache.org/jira/browse/CASSANDRA-2478
> Project: Cassandra
> Issue Type: New Feature
> Components: API, Core
> Reporter: Eric Evans
> Assignee: Sylvain Lebresne
> Priority: Minor
> Labels: cql
> Fix For: 1.2
>
> Attachments: cql_binary_protocol, cql_binary_protocol-v2
>
>
> A custom wire protocol would give us the flexibility to optimize for our
> specific use-cases, and eliminate a troublesome dependency (I'm referring to
> Thrift, but none of the others would be significantly better). Additionally,
> RPC is bad fit here, and we'd do better to move in the direction of something
> that natively supports streaming.
> I don't think this is as daunting as it might seem initially. Utilizing an
> existing server framework like Netty, combined with some copy-and-paste of
> bits from other FLOSS projects would probably get us 80% of the way there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
