That actually is a good point. <div><br></div><div>That probably means that we have to use special parser for JSON Encryption Envelope. </div><div><br></div><div>Do you have any other suggestion? </div><div><br></div><div>
=nat<br><br><div class="gmail_quote">On Tue, Sep 28, 2010 at 4:00 PM, nara hideki <span dir="ltr"><<a href="mailto:hdknr@ic-tact.co.jp">hdknr@ic-tact.co.jp</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi all<br>
<br>
I'm thinking of using JSON Encryption Envelope to encrypt responding data.<br>
(<a href="http://jsonenc.info/1.0/" target="_blank">http://jsonenc.info/1.0/</a> )<br>
<br>
Most of privacy data provided by CX data endpoint must not be so big,<br>
but some huge JSON may cause some problem<br>
because streaming JSON readers or parsers are not so popular.<br>
<br>
I'd be happy to have some good idea about that.<br>
<br>
Thanks in advance.<br>
----<br>
hdknr<br>
_______________________________________________<br>
Specs-cx mailing list<br>
<a href="mailto:Specs-cx@lists.openid.net">Specs-cx@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs-cx" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs-cx</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Nat Sakimura (=nat)<br><a href="http://www.sakimura.org/en/">http://www.sakimura.org/en/</a><br><a href="http://twitter.com/_nat_en">http://twitter.com/_nat_en</a><br>
</div>