I agree with Luke that HTTP standard has everything necessary and bloating payload with json/xml is not necessary.<div><br></div><div>Btw that argument &quot;we have json in client already&quot; seems pretty wrong, because json in server rpc solves another problem (and solve it in wrong way, because of data type issues, but it&#39;s another story).</div>

<div><br></div><div>slush<br><br><div class="gmail_quote">On Mon, Dec 19, 2011 at 6:04 PM, Jordan Mack <span dir="ltr">&lt;<a href="mailto:jordanmack@parhelic.com">jordanmack@parhelic.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

I thought that JSON support was fairly common these days. I personally<br>
prefer XML in most cases, but since JSON is already used with the RPC,<br>
it seemed like a natural fit here. Binary data can be base64 encoded,<br>
although I&#39;m not sure why you would need to send back binary in an alias<br>
response.<br></blockquote></div></div>