JysonCompliance » History » Version 1
Alan Kennedy, 2009-03-17 08:58 PM
1 | 1 | Alan Kennedy | h1. Compliance of jyson |
---|---|---|---|
2 | |||
3 | There are two main areas where jyson needs to be compliant. |
||
4 | |||
5 | h2. RFC 4627 |
||
6 | |||
7 | JSON was originally specified with a simple syntax diagram on "JSON.org":http://json.org |
||
8 | |||
9 | As JSON became more and more widely used, an internet RFC was published by Douglas Crockford, the original creator of JSON. That document is "RFC 4627":http://www.ietf.org/rfc/rfc4627.txt , which is now the definitive specification for JSON. |
||
10 | |||
11 | I am currently conducting a review of jyson's compliance with RFC 4627. |
||
12 | |||
13 | h2. The cpython json module. |
||
14 | |||
15 | I originally wrote jyson back in 2005, and devised my own API. |
||
16 | |||
17 | Now, there is a "json module":http://docs.python.org/library/json.html in the cpython standard library, as of version 2.6. Which means that jython will need to have a json module when it reaches version 2.6. This may be achieved by running the pure python version of the json module (the cpython json module relies on C extensions for some of it's speed). |
||
18 | |||
19 | But the C extensions won't run on jython, meaning that jython will suffer a speed penalty running the existing pure python module. |
||
20 | |||
21 | If jyson can be made to implement the same API as the cpython json module, then I will contribute the module to jython. |
||
22 | |||
23 | Here is a list of the main areas in which there are differences between the APIs |
||
24 | |||
25 | # TBD |
||
26 | # TBD |
||
27 | # TBD |