JSON is a great way to make your data accessible to deep packet scanning systems. Define all your protocols with JSON!
ECMA-404: The JSON Data Interchange Format [pdf]
41–50 of 199 posts
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#42Does this mean we can now use it for evil?
That license issue wasn't about the spec, it was about the implementation. Alas.
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#43Earlier quoted context omitted.
Nope, sorry.
This sucks, because it limits the usability of JSON. It should interfere with its being a serialization and interchange format, but for configuration files anything without comments is useless.
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#44Why can the solidus (/) be escaped?
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#45Earlier quoted context omitted.
Why do you ask him without the stubborn and arrogant comment on G+ and about trailing commas? Or is indirect better?
Trailing commas would make the problem worse! If you allow trailing commas then you would break json parsing in all old version of IE. The unicode line ending problem is more subtle. I have seen people write code like (mix javascript and some templating): var prefs = ; ... The above code looks okay, but if the json is just spec conforming, then you are exposed to a potential XSS attack. Most people that write json en…
> If you allow trailing commas then you would break json parsing in all old version of IE.
No, you would break the evaluation of json as javascript in old versions of IE.
Use a real parser already.
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#46My faint hopes for trailing comma support are now crushed.
What does trailing comma support get you?
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#47Earlier quoted context omitted.
Trailing commas would make the problem worse! If you allow trailing commas then you would break json parsing in all old version of IE. The unicode line ending problem is more subtle. I have seen people write code like (mix javascript and some templating): var prefs = ; ... The above code looks okay, but if the json is just spec conforming, then you are exposed to a potential XSS attack. Most people that write json en…
> you would break json parsing in all old version of IE Why do people still care about old versions of IE?
They don't, it's just convenient to make their point. Pretty much any new technology isn't directly compatible with old technology.
Re: ECMA-404: The JSON Data Interchange Format [pdf]
#48Re: ECMA-404: The JSON Data Interchange Format [pdf]
#49Earlier quoted context omitted.
Nope, sorry.
This sucks, because it limits the usability of JSON. It should interfere with its being a serialization and interchange format, but for configuration files anything without comments is useless.
Not really... just add a "comment" key and then ignore it when processing.