[Specs-cx] JSON Encryption Envelope

[nara hideki]

Because encrypted text tend to be smaller than original text, problem
are there when original text is too big.
If the original text is structured text like JSON or XML,  the size is
limited to container object in programming runtime.
So if original texts have some negotiation parameter like paging or
siblings flags, applications can work together. It simply is an
application matter.

But if sending party writes data in simple text streaming like
"printf",  "enc_data" in JSON Encryption Envelope can be too big and
cause some problem at receiver side.

---
hdknr

2010/9/29 Nat Sakimura <sakimura at gmail.com>:
> That actually is a good point.
> That probably means that we have to use special parser for JSON Encryption
> Envelope.
> Do you have any other suggestion?
> =nat
>
> On Tue, Sep 28, 2010 at 4:00 PM, nara hideki <hdknr at ic-tact.co.jp> wrote:
>>
>> Hi all
>>
>> I'm thinking of using JSON Encryption Envelope to encrypt responding data.
>> (http://jsonenc.info/1.0/ )
>>
>> Most of privacy data provided by CX data endpoint must not be so big,
>> but some huge JSON may cause some problem
>> because  streaming JSON readers or parsers are not so popular.
>>
>> I'd be happy to have some good idea about that.
>>
>> Thanks in advance.
>> ----
>> hdknr
>> _______________________________________________
>> Specs-cx mailing list
>> Specs-cx at lists.openid.net
>> http://lists.openid.net/mailman/listinfo/openid-specs-cx
>
>
>
> --
> Nat Sakimura (=nat)
> http://www.sakimura.org/en/
> http://twitter.com/_nat_en
>