Difference between revisions of "Documentation"
From DJSON
| Line 2: | Line 2: | ||
* [[Draft Jenkins JMAP]] | * [[Draft Jenkins JMAP]] | ||
| + | |||
| + | * [[Draft Jenkins JMAPmail]] | ||
* http://rfc7159.net/rfc7159#rfc.section.1.2 JSON Specifications (from RFC 7159) | * http://rfc7159.net/rfc7159#rfc.section.1.2 JSON Specifications (from RFC 7159) | ||
Revision as of 12:04, 26 February 2017
- http://rfc7159.net/rfc7159#rfc.section.1.2 JSON Specifications (from RFC 7159)
- RFC 7159 - Référence IETF en vérification actuelle. http://rfc7159.net/rfc7159#rfc.section.1.2
- Parsing JSON Nicolas Seriot - Référence d'analyse pour le IETF/WG sur JSON.
- JSON is the de facto standard when it comes to (un)serialising and exchanging data in web and mobile programming. But how well do you really know JSON? We'll read the specifications and write test cases together. We'll test common JSON libraries against our test cases. I'll show that JSON is not the easy, idealised format as many do believe. Indeed, I did not find two libraries that exhibit the very same behaviour. Moreover, I found that edge cases and maliciously crafted payloads can cause bugs, crashes and denial of services, mainly because JSON libraries rely on specifications that have evolved over time and that left many details loosely specified or not specified at all.
- IETF WG Datatracker on 'JSONbis
