cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-754) Pluggable API with a simple HTTP+JSON daemon
Date Mon, 15 Feb 2010 19:21:28 GMT


Jonathan Ellis commented on CASSANDRA-754:

> I don't think this project will ever want to support >2 transports because it is a
lot of work.

Right. We've already seen the problems multiple transports cause as I've de-synced Avro from
the "main" Thrift protocol in e.g. CASSANDRA-775.  I don't think we want to throw the doors
open and say "just implement this interface, the more the merrier" because that would really
get nightmarish if people actually did.  Nor do we want to just leave it in contrib to be
half-supported; that would be a big turn-off for people investigating the project.

So I am +0 on cleaning up common code that we already have w/ thrift+avro (although I think
Gary is right re pushing logic into setup methods) but -1 on adding a new interface/protocol
without seeing a clear benefit over avro/thrift (which, again, can work over HTTP+JSON already).

> Pluggable API with a simple HTTP+JSON daemon
> --------------------------------------------
>                 Key: CASSANDRA-754
>                 URL:
>             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.

View raw message