[
https://issues.apache.org/jira/browse/CASSANDRA-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833170#action_12833170
]
Gary Dusbabek commented on CASSANDRA-754:
-----------------------------------------
Thanks Ted. bin/cassandra needs to be tweaked to supply the right class name,
but that is trivial. Also, I don't see the point of allowing more than one api
instance to be active per VM.
It seems that we skipped the "is this right for cassandra" discussion, and I'm
worried you might be addressing a non-problem. Can you explain what you're
attempting to address here, and how it benefits?
The only reason I can see moving forward with this is if we're *really* serious
about giving other transport and RPC mechanisms the same first-class treatment
as thrift. If we are, there is a lot more work to get done before the work
done in this patch.
> 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
>
>
> 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.
