[
https://issues.apache.org/jira/browse/CASSANDRA-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833893#action_12833893
]
Gary Dusbabek commented on CASSANDRA-754:
-----------------------------------------
With avro, the idea is that at some point it will deprecate thrift and
eventually (maybe) replace it entirely. I don't think this project will ever
want to support >2 transports because it is a lot of work. (We still have to
work around problems with thrift, and using avro is turning out to be a fair
amount of work.) Making the transport pluggable implies that the community is
willing to support that. Are we?
I'm not against the changes from a code organization or architecture
standpoint. I just think we should limit the transports we allow for the sake
of support.
> Pluggable API with a simple HTTP+JSON daemon
> --------------------------------------------
>
> Key: CASSANDRA-754
> URL: https://issues.apache.org/jira/browse/CASSANDRA-754
> Project: Cassandra
> Issue Type: New Feature
> Components: Core
> Reporter: Ted Zlatanov
> Priority: Minor
> Attachments: 001-CASSANDRA-754-api-reorg.patch,
> 001-CASSANDRA-754-api-reorg.patch, 002-CASSANDRA-754-thriftdaemon.patch,
> 002-CASSANDRA-754-thriftdaemon.patch, 003-CASSANDRA-754-configapi.patch,
> 003-CASSANDRA-754-configapi.patch, 004-CASSANDRA-754-onedaemon.patch,
> 005-CASSANDRA-754-avroconfig.patch, 006-CASSANDRA-754-daemonproperties.patch,
> 006-CASSANDRA-754-daemonproperties.patch,
> 007-CASSANDRA-754-stringproperties.patch,
> 100-CASSANDRA-754-rebased-api-reorg.patch, 101-CASSANDRA-754-binclass.patch
>
>
> Proposal of a simple pluggable API interface with a HTTP daemon implementation
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
