Mailing-List: contact client-dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: client-dev@cassandra.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Subject: Re: Avro RPC?
From: Eric Evans <eevans@rackspace.com>
To: dev@cassandra.apache.org
Cc: client-dev@cassandra.apache.org
In-Reply-To: <AANLkTimk_8ut8=mH6ezLDg9VG2G1w-N9oyLrd5g0EEbb@mail.gmail.com>
References: <1293037253.11611.85.camel@erebus.lan>
	 <AANLkTimk_8ut8=mH6ezLDg9VG2G1w-N9oyLrd5g0EEbb@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Date: Wed, 22 Dec 2010 11:40:21 -0600
Message-ID: <1293039621.11611.92.camel@erebus.lan>
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit

On Wed, 2010-12-22 at 17:27 +0000, Jools wrote:
> It's interesting to note that in Eben Hewitt's - The definitive guide
> to Cassandra he states the following;
> 
> *Avro Summary*
> 
> As of Cassandra version 0.7, Avro is the RPC and data serialization
> mechanism for Cassandra.
> 
> It generates code that remote clients can use to interact with the
> database.
> 
> It’s well-supported in the community and has the strength of growing
> out of the larger and very well-known Hadoop project.
> 
> It should serve Cassandra well for the foreseeable future.

Huh.  That's just... wrong.

> Personally I'm pretty much married to thrift as it's used all the way
> through my application stack, and having played with Avro it really
> didn't merit the effort to move over (for me at least).
> 
> How are you thinking of creating an 'application specific' transport?

Not sure what you mean, by "how" here.  I haven't written a spec yet, if
that's what you mean.

-- 
Eric Evans
eevans@rackspace.com