You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Ryan King (JIRA)" <ji...@apache.org> on 2011/08/22 20:45:29 UTC

[jira] [Commented] (CASSANDRA-2478) Custom protocol/transport

    [ https://issues.apache.org/jira/browse/CASSANDRA-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088918#comment-13088918 ] 

Ryan King commented on CASSANDRA-2478:
--------------------------------------

If you want to use netty, I'd suggest considering using finagle on top of it: http://github.com/twitter/finagle. Its written in scala but its very easy to use from java.

> Custom 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
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira