Re: [Json] The names within an object SHOULD be unique.

[Tatu Saloranta <[e-mail]>]

On Wed, Jun 5, 2013 at 1:59 PM, Vinny A <[e-mail]> wrote:

>
> On Jun 5, 2013, at 2:30 PM, Stephan Beal <[e-mail]> wrote:
>
> It gives implementations leeway on what is essentially a corner case (who
> actively generates non-unique keys?). Forcing a specific behaviour here
> could potentially leave a lot of current 100% JSON-compliant parsers
> suddenly non-compliant because of [what i perceive as] an unusual corner
> case.
>
>
> If parsers are accepting duplicate keys, they're already non-compliant.
> RFC 4627 states that keys should be unique, and the org.json reference
> parser throws an exception when it hits a duplicate key (line 1186 in
> JSONObject).
>
>
Doing this is fine, but requiring verification is quite another thing. It
opens a new possibility for DoS attacks, if parser (tokenizer) has to
verify this invariant, as it must keep all seen names for all open objects
in memory. From user perspective this also seems like pure overhead; and
non-trivial amount as well, for fast data-binding maintaining hash set may
take as much time as data-binding.

-+ Tatu +-