You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@avro.apache.org by cu...@apache.org on 2009/06/30 23:46:26 UTC
svn commit: r789974 - in /hadoop/avro/trunk: CHANGES.txt
src/doc/content/xdocs/spec.xml
Author: cutting
Date: Tue Jun 30 21:46:26 2009
New Revision: 789974
URL: http://svn.apache.org/viewvc?rev=789974&view=rev
Log:
AVRO-67. Add per-call RPC metadata to spec. George Porter via cutting.
Modified:
hadoop/avro/trunk/CHANGES.txt
hadoop/avro/trunk/src/doc/content/xdocs/spec.xml
Modified: hadoop/avro/trunk/CHANGES.txt
URL: http://svn.apache.org/viewvc/hadoop/avro/trunk/CHANGES.txt?rev=789974&r1=789973&r2=789974&view=diff
==============================================================================
--- hadoop/avro/trunk/CHANGES.txt (original)
+++ hadoop/avro/trunk/CHANGES.txt Tue Jun 30 21:46:26 2009
@@ -44,6 +44,8 @@
AVRO-29. Add to Java a validating encoder & decoder, and a
resolving decoder. (Thiruvalluvan M. G. & Raymie Stata)
+ AVRO-67. Add per-call RPC metadata to spec. (George Porter via cutting)
+
IMPROVEMENTS
AVRO-11. Re-implement specific and reflect datum readers and
Modified: hadoop/avro/trunk/src/doc/content/xdocs/spec.xml
URL: http://svn.apache.org/viewvc/hadoop/avro/trunk/src/doc/content/xdocs/spec.xml?rev=789974&r1=789973&r2=789974&view=diff
==============================================================================
--- hadoop/avro/trunk/src/doc/content/xdocs/spec.xml (original)
+++ hadoop/avro/trunk/src/doc/content/xdocs/spec.xml Tue Jun 30 21:46:26 2009
@@ -736,12 +736,15 @@
<section>
<title>Call Format</title>
- <p>An <em>call</em> consists of a request message paired with
- its resulting response or error message. Both kinds of
+ <p>A <em>call</em> consists of a request message paired with
+ its resulting response or error message. Requests and
+ responses contain extensible metadata, and both kinds of
messages are framed as described above.</p>
<p>The format of a call request is:</p>
<ul>
+ <li><em>request metadata</em>, a map with values of
+ type <code>bytes</code></li>
<li>the <em>message name</em>, an Avro string,
followed by</li>
<li>the message <em>parameters</em>. Parameters are
@@ -751,6 +754,8 @@
<p>The format of a call response is:</p>
<ul>
+ <li><em>response metadata</em>, a map with values of
+ type <code>bytes</code></li>
<li>a one-byte <em>error flag</em> boolean, followed by either:
<ul>
<li>if the error flag is false, the message <em>response</em>,