[ https://issues.apache.org/jira/browse/CASSANDRA-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408053#comment-13408053 ]
Holger Hoffstätte commented on CASSANDRA-2478: ---------------------------------------------- Sylvain, thanks for the explanation - makes perfect sense, though I disagree :-) In my experiene every protocol that starts with fully-synchronous interactions eventually has to bite that bullet. I agree though that it's not the most important thing right now and other ways of coordinating client<->cluster interactions could be much more beneficial and efficient. As for response frames I don't see how you could handle two interleaved queries (first slow, second fast but "blocked from returning" by the previous one) without command/response correlation; there can only be a single query to a node in flight at a time. > 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