Return-Path: 
 <dev-return-3056-apmail-cassandra-dev-archive=cassandra.apache.org@cassandra.apache.org>
Delivered-To: apmail-cassandra-dev-archive@www.apache.org
Received: (qmail 12777 invoked from network); 22 Dec 2010 17:53:22 -0000
Received: from unknown (HELO mail.apache.org) (140.211.11.3)
  by 140.211.11.9 with SMTP; 22 Dec 2010 17:53:22 -0000
Received: (qmail 79066 invoked by uid 500); 22 Dec 2010 17:53:21 -0000
Delivered-To: apmail-cassandra-dev-archive@cassandra.apache.org
Received: (qmail 79026 invoked by uid 500); 22 Dec 2010 17:53:21 -0000
Mailing-List: contact dev-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@cassandra.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@cassandra.apache.org>
List-Post: <mailto:dev@cassandra.apache.org>
List-Id: <dev.cassandra.apache.org>
Reply-To: dev@cassandra.apache.org
Delivered-To: mailing list dev@cassandra.apache.org
Received: (qmail 79010 invoked by uid 99); 22 Dec 2010 17:53:21 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Dec 2010 17:53:21 +0000
X-ASF-Spam-Status: No, hits=1.5 required=10.0
	tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of javier.canillas@gmail.com
 designates 209.85.213.172 as permitted sender)
Received: from [209.85.213.172] (HELO mail-yx0-f172.google.com)
 (209.85.213.172)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Dec 2010 17:53:14 +0000
Received: by yxt33 with SMTP id 33so2517976yxt.31
        for <multiple recipients>; Wed, 22 Dec 2010 09:52:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:received:in-reply-to
         :references:date:message-id:subject:from:to:cc:content-type;
        bh=t6CMJo3CdaNZ8q3yEOSKGnU2ZLBXTn4r2cMqUPMsUZM=;
        b=rS+J+Oz2D4HoOWmTR/M6NOx5q46PlWRRQfAce9xuRe7wObUiinuL162n7J1STm5ltF
         ERqYUEiKrY8F2sQUAYYu5O9Vocx6oBUd2Ui5UHUwnvavHzBxeBfLTC7S4aTcjHlGA2+D
         yKsPIwM73SEQgE54TAm+WG7e/m/t5BPs9Otik=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=d9HVBJd+NP8ogblZUs+qi95+Sactzlv4hI0n4A2tT+O0VKa++DMbM1D9QXkb20XDhT
         YRIYZOKb36QVZvDsFmVt8ZjjCq0Xj4DBDHxNBGMJSNBplHU8TnBASu1t/2ZvAE4vdMm5
         Ya91hzmN6ZLpNPXv8IlIHqw0Qmdqmf7UqeY4o=
MIME-Version: 1.0
Received: by 10.236.111.38 with SMTP id v26mr11172340yhg.18.1293040373281;
 Wed, 22 Dec 2010 09:52:53 -0800 (PST)
Received: by 10.236.103.132 with HTTP; Wed, 22 Dec 2010 09:52:53 -0800 (PST)
In-Reply-To: <1293039621.11611.92.camel@erebus.lan>
References: <1293037253.11611.85.camel@erebus.lan>
	<AANLkTimk_8ut8=mH6ezLDg9VG2G1w-N9oyLrd5g0EEbb@mail.gmail.com>
	<1293039621.11611.92.camel@erebus.lan>
Date: Wed, 22 Dec 2010 14:52:53 -0300
Message-ID: <AANLkTik6yDOdAZpuNdUZTRFYRz==QN0hc-Mx5Bd6ZQxP@mail.gmail.com>
Subject: Re: Avro RPC?
From: Kani <javier.canillas@gmail.com>
To: dev@cassandra.apache.org
Cc: client-dev@cassandra.apache.org
Content-Type: multipart/alternative; boundary=0023547c8e512133000498036cc7
X-Virus-Checked: Checked by ClamAV on apache.org

--0023547c8e512133000498036cc7
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

As a C# client maintainer, I have based Aquiles to work with Thrift than
AVRO, since there is no support for AVRO on C# yet.
Check: https://issues.apache.org/jira/browse/AVRO-533

<https://issues.apache.org/jira/browse/AVRO-533>Another thing you may check=
,
if you are thinking on a new protocol for comunication is Hessian (
http://en.wikipedia.org/wiki/Hessian_(web_service_protocol))

In my opinion, I would mantain Thrift, since it's fair enough for what we
need right now and probably most of the actual developed clients are based
on it.


On Wed, Dec 22, 2010 at 2:40 PM, Eric Evans <eevans@rackspace.com> wrote:

> 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=E2=80=99s well-supported in the community and has the strength of gr=
owing
> > 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
>
>

--0023547c8e512133000498036cc7--