Mailing-List: contact user-help@avro.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@avro.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type;
  b=dZv9L1ebQBjGj0fYfNEUvo55mSaXGfiNlvHRYcwZHYzUVbnGK/8zMPSr/H1KfSXzduJ3qbkjJZunzlc6+2n9SUYfCE8bHJWABtu+6700crGyVDOTC+boMYzDfjb9rwUl7CnXoF7pj/ylEA8PXMerNlbjrEQa8xheiOFLeHyoLjg=;
Message-ID: <1353533498.84034.YahooMailNeo@web126201.mail.ne1.yahoo.com>
Date: Wed, 21 Nov 2012 13:31:38 -0800 (PST)
From: Brian Lee <leeb_08@yahoo.com>
Reply-To: Brian Lee <leeb_08@yahoo.com>
Subject: any movement on JSON encoding for RPC?
To: "user@avro.apache.org" <user@avro.apache.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="-606767240-1059687176-1353533498=:84034"

---606767240-1059687176-1353533498=:84034
Content-Type: text/plain; charset=us-ascii

I found a message from last year that JSON encoding for RPC was not yet implemented. Is this still the case? If so, this would be very bad as one of the selling points we were using is that Avro serialized its messages in JSON format.

Brian

---606767240-1059687176-1353533498=:84034
Content-Type: text/html; charset=us-ascii

<html><body><div style="color:#000; background-color:#fff; font-family:arial, helvetica, sans-serif;font-size:10pt">I found a message from last year that JSON encoding for RPC was not yet implemented. Is this still the case? If so, this would be very bad as one of the selling points we were using is that Avro serialized its messages in JSON format.<br><br>Brian<br></div></body></html>
---606767240-1059687176-1353533498=:84034--