[
https://issues.apache.org/jira/browse/CASSANDRA-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13163611#comment-13163611
]
Piotr Kołaczkowski edited comment on CASSANDRA-2478 at 12/6/11 2:20 PM:
------------------------------------------------------------------------
Have you considered Hessian? Or taking some parts of it - because it is
open-source and quite simple. We used it as the main platform for webservices
at our company (mostly doing MMORPG games). It is very lightweight, it supports
streaming, it supports many programming languages, it would be possible to run
using Jetty or Netty (we used Jetty). However, it doesn't support versioning,
so it would have to be improved.
was (Author: pkolaczk):
Have you considered Hessian? Or taking some parts of it - because it is
open-source and quite simple. We used it as the main platform for webservices
at our company (mostly doing MMORPG games). It is very lightweight, it supports
streaming, it supports many programming languages. However, it doesn't support
versioning, so it would have to be improved.
> 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
