[
https://issues.apache.org/jira/browse/CASSANDRA-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13183358#comment-13183358
]
Eric Evans commented on CASSANDRA-2478:
---------------------------------------
{quote}
I don't see any other right off the bat, but between those two I would have a
slight preference for a custom protocol. My (to be honest not so extensive)
experience with HTTP is that it can be slowish and a tad annoying to work with
when you use it for something it wasn't designed for (typically streaming is
not a given). But a custom protocol will clearly be more work for us. I just
have a feeling that it may be worth it in the end.
And whether it is HTTP or custom, I've had good experience with Netty in the
past too.
{quote}
+1
> 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
> Priority: Minor
> Labels: cql
>
> 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
