… | |
… | |
37 | primary goal is to be I<correct> and its secondary goal is to be |
37 | primary goal is to be I<correct> and its secondary goal is to be |
38 | I<fast>. To reach the latter goal it was written in C. |
38 | I<fast>. To reach the latter goal it was written in C. |
39 | |
39 | |
40 | Beginning with version 2.0 of the JSON module, when both JSON and |
40 | Beginning with version 2.0 of the JSON module, when both JSON and |
41 | JSON::XS are installed, then JSON will fall back on JSON::XS (this can be |
41 | JSON::XS are installed, then JSON will fall back on JSON::XS (this can be |
42 | overriden) with no overhead due to emulation (by inheritign constructor |
42 | overridden) with no overhead due to emulation (by inheriting constructor |
43 | and methods). If JSON::XS is not available, it will fall back to the |
43 | and methods). If JSON::XS is not available, it will fall back to the |
44 | compatible JSON::PP module as backend, so using JSON instead of JSON::XS |
44 | compatible JSON::PP module as backend, so using JSON instead of JSON::XS |
45 | gives you a portable JSON API that can be fast when you need and doesn't |
45 | gives you a portable JSON API that can be fast when you need and doesn't |
46 | require a C compiler when that is a problem. |
46 | require a C compiler when that is a problem. |
47 | |
47 | |
… | |
… | |
49 | to write yet another JSON module? While it seems there are many JSON |
49 | to write yet another JSON module? While it seems there are many JSON |
50 | modules, none of them correctly handle all corner cases, and in most cases |
50 | modules, none of them correctly handle all corner cases, and in most cases |
51 | their maintainers are unresponsive, gone missing, or not listening to bug |
51 | their maintainers are unresponsive, gone missing, or not listening to bug |
52 | reports for other reasons. |
52 | reports for other reasons. |
53 | |
53 | |
54 | See COMPARISON, below, for a comparison to some other JSON modules. |
|
|
55 | |
|
|
56 | See MAPPING, below, on how JSON::XS maps perl values to JSON values and |
54 | See MAPPING, below, on how JSON::XS maps perl values to JSON values and |
57 | vice versa. |
55 | vice versa. |
58 | |
56 | |
59 | =head2 FEATURES |
57 | =head2 FEATURES |
60 | |
58 | |
… | |
… | |
65 | This module knows how to handle Unicode, documents how and when it does |
63 | This module knows how to handle Unicode, documents how and when it does |
66 | so, and even documents what "correct" means. |
64 | so, and even documents what "correct" means. |
67 | |
65 | |
68 | =item * round-trip integrity |
66 | =item * round-trip integrity |
69 | |
67 | |
70 | When you serialise a perl data structure using only datatypes supported |
68 | When you serialise a perl data structure using only data types supported |
71 | by JSON, the deserialised data structure is identical on the Perl level. |
69 | by JSON and Perl, the deserialised data structure is identical on the Perl |
72 | (e.g. the string "2.0" doesn't suddenly become "2" just because it looks |
70 | level. (e.g. the string "2.0" doesn't suddenly become "2" just because |
73 | like a number). There minor I<are> exceptions to this, read the MAPPING |
71 | it looks like a number). There I<are> minor exceptions to this, read the |
74 | section below to learn about those. |
72 | MAPPING section below to learn about those. |
75 | |
73 | |
76 | =item * strict checking of JSON correctness |
74 | =item * strict checking of JSON correctness |
77 | |
75 | |
78 | There is no guessing, no generating of illegal JSON texts by default, |
76 | There is no guessing, no generating of illegal JSON texts by default, |
79 | and only JSON is accepted as input by default (the latter is a security |
77 | and only JSON is accepted as input by default (the latter is a security |
… | |
… | |
84 | Compared to other JSON modules and other serialisers such as Storable, |
82 | Compared to other JSON modules and other serialisers such as Storable, |
85 | this module usually compares favourably in terms of speed, too. |
83 | this module usually compares favourably in terms of speed, too. |
86 | |
84 | |
87 | =item * simple to use |
85 | =item * simple to use |
88 | |
86 | |
89 | This module has both a simple functional interface as well as an objetc |
87 | This module has both a simple functional interface as well as an object |
90 | oriented interface interface. |
88 | oriented interface interface. |
91 | |
89 | |
92 | =item * reasonably versatile output formats |
90 | =item * reasonably versatile output formats |
93 | |
91 | |
94 | You can choose between the most compact guaranteed-single-line format |
92 | You can choose between the most compact guaranteed-single-line format |
95 | possible (nice for simple line-based protocols), a pure-ascii format |
93 | possible (nice for simple line-based protocols), a pure-ASCII format |
96 | (for when your transport is not 8-bit clean, still supports the whole |
94 | (for when your transport is not 8-bit clean, still supports the whole |
97 | Unicode range), or a pretty-printed format (for when you want to read that |
95 | Unicode range), or a pretty-printed format (for when you want to read that |
98 | stuff). Or you can combine those features in whatever way you like. |
96 | stuff). Or you can combine those features in whatever way you like. |
99 | |
97 | |
100 | =back |
98 | =back |
101 | |
99 | |
102 | =cut |
100 | =cut |
103 | |
101 | |
104 | package JSON::XS; |
102 | package JSON::XS; |
105 | |
103 | |
106 | use strict; |
104 | use common::sense; |
107 | |
105 | |
108 | our $VERSION = '2.2'; |
106 | our $VERSION = '2.29'; |
109 | our @ISA = qw(Exporter); |
107 | our @ISA = qw(Exporter); |
110 | |
108 | |
111 | our @EXPORT = qw(encode_json decode_json to_json from_json); |
109 | our @EXPORT = qw(encode_json decode_json to_json from_json); |
112 | |
110 | |
113 | sub to_json($) { |
111 | sub to_json($) { |
… | |
… | |
137 | |
135 | |
138 | This function call is functionally identical to: |
136 | This function call is functionally identical to: |
139 | |
137 | |
140 | $json_text = JSON::XS->new->utf8->encode ($perl_scalar) |
138 | $json_text = JSON::XS->new->utf8->encode ($perl_scalar) |
141 | |
139 | |
142 | except being faster. |
140 | Except being faster. |
143 | |
141 | |
144 | =item $perl_scalar = decode_json $json_text |
142 | =item $perl_scalar = decode_json $json_text |
145 | |
143 | |
146 | The opposite of C<encode_json>: expects an UTF-8 (binary) string and tries |
144 | The opposite of C<encode_json>: expects an UTF-8 (binary) string and tries |
147 | to parse that as an UTF-8 encoded JSON text, returning the resulting |
145 | to parse that as an UTF-8 encoded JSON text, returning the resulting |
… | |
… | |
149 | |
147 | |
150 | This function call is functionally identical to: |
148 | This function call is functionally identical to: |
151 | |
149 | |
152 | $perl_scalar = JSON::XS->new->utf8->decode ($json_text) |
150 | $perl_scalar = JSON::XS->new->utf8->decode ($json_text) |
153 | |
151 | |
154 | except being faster. |
152 | Except being faster. |
155 | |
153 | |
156 | =item $is_boolean = JSON::XS::is_bool $scalar |
154 | =item $is_boolean = JSON::XS::is_bool $scalar |
157 | |
155 | |
158 | Returns true if the passed scalar represents either JSON::XS::true or |
156 | Returns true if the passed scalar represents either JSON::XS::true or |
159 | JSON::XS::false, two constants that act like C<1> and C<0>, respectively |
157 | JSON::XS::false, two constants that act like C<1> and C<0>, respectively |
… | |
… | |
197 | |
195 | |
198 | If you didn't know about that flag, just the better, pretend it doesn't |
196 | If you didn't know about that flag, just the better, pretend it doesn't |
199 | exist. |
197 | exist. |
200 | |
198 | |
201 | =item 4. A "Unicode String" is simply a string where each character can be |
199 | =item 4. A "Unicode String" is simply a string where each character can be |
202 | validly interpreted as a Unicode codepoint. |
200 | validly interpreted as a Unicode code point. |
203 | |
201 | |
204 | If you have UTF-8 encoded data, it is no longer a Unicode string, but a |
202 | If you have UTF-8 encoded data, it is no longer a Unicode string, but a |
205 | Unicode string encoded in UTF-8, giving you a binary string. |
203 | Unicode string encoded in UTF-8, giving you a binary string. |
206 | |
204 | |
207 | =item 5. A string containing "high" (> 255) character values is I<not> a UTF-8 string. |
205 | =item 5. A string containing "high" (> 255) character values is I<not> a UTF-8 string. |
… | |
… | |
442 | the same JSON text (given the same overall settings). If it is disabled, |
440 | the same JSON text (given the same overall settings). If it is disabled, |
443 | the same hash might be encoded differently even if contains the same data, |
441 | the same hash might be encoded differently even if contains the same data, |
444 | as key-value pairs have no inherent ordering in Perl. |
442 | as key-value pairs have no inherent ordering in Perl. |
445 | |
443 | |
446 | This setting has no effect when decoding JSON texts. |
444 | This setting has no effect when decoding JSON texts. |
|
|
445 | |
|
|
446 | This setting has currently no effect on tied hashes. |
447 | |
447 | |
448 | =item $json = $json->allow_nonref ([$enable]) |
448 | =item $json = $json->allow_nonref ([$enable]) |
449 | |
449 | |
450 | =item $enabled = $json->get_allow_nonref |
450 | =item $enabled = $json->get_allow_nonref |
451 | |
451 | |
… | |
… | |
701 | =back |
701 | =back |
702 | |
702 | |
703 | |
703 | |
704 | =head1 INCREMENTAL PARSING |
704 | =head1 INCREMENTAL PARSING |
705 | |
705 | |
706 | [This section and the API it details is still EXPERIMENTAL] |
|
|
707 | |
|
|
708 | In some cases, there is the need for incremental parsing of JSON |
706 | In some cases, there is the need for incremental parsing of JSON |
709 | texts. While this module always has to keep both JSON text and resulting |
707 | texts. While this module always has to keep both JSON text and resulting |
710 | Perl data structure in memory at one time, it does allow you to parse a |
708 | Perl data structure in memory at one time, it does allow you to parse a |
711 | JSON stream incrementally. It does so by accumulating text until it has |
709 | JSON stream incrementally. It does so by accumulating text until it has |
712 | a full JSON object, which it then can decode. This process is similar to |
710 | a full JSON object, which it then can decode. This process is similar to |
713 | using C<decode_prefix> to see if a full JSON object is available, but is |
711 | using C<decode_prefix> to see if a full JSON object is available, but |
714 | much more efficient (JSON::XS will only attempt to parse the JSON text |
712 | is much more efficient (and can be implemented with a minimum of method |
|
|
713 | calls). |
|
|
714 | |
|
|
715 | JSON::XS will only attempt to parse the JSON text once it is sure it |
715 | once it is sure it has enough text to get a decisive result, using a very |
716 | has enough text to get a decisive result, using a very simple but |
716 | simple but truly incremental parser). |
717 | truly incremental parser. This means that it sometimes won't stop as |
|
|
718 | early as the full parser, for example, it doesn't detect parenthese |
|
|
719 | mismatches. The only thing it guarantees is that it starts decoding as |
|
|
720 | soon as a syntactically valid JSON text has been seen. This means you need |
|
|
721 | to set resource limits (e.g. C<max_size>) to ensure the parser will stop |
|
|
722 | parsing in the presence if syntax errors. |
717 | |
723 | |
718 | The following two methods deal with this. |
724 | The following methods implement this incremental parser. |
719 | |
725 | |
720 | =over 4 |
726 | =over 4 |
721 | |
727 | |
722 | =item [void, scalar or list context] = $json->incr_parse ([$string]) |
728 | =item [void, scalar or list context] = $json->incr_parse ([$string]) |
723 | |
729 | |
… | |
… | |
745 | objects or arrays, instead they must be concatenated back-to-back. If |
751 | objects or arrays, instead they must be concatenated back-to-back. If |
746 | an error occurs, an exception will be raised as in the scalar context |
752 | an error occurs, an exception will be raised as in the scalar context |
747 | case. Note that in this case, any previously-parsed JSON texts will be |
753 | case. Note that in this case, any previously-parsed JSON texts will be |
748 | lost. |
754 | lost. |
749 | |
755 | |
|
|
756 | Example: Parse some JSON arrays/objects in a given string and return |
|
|
757 | them. |
|
|
758 | |
|
|
759 | my @objs = JSON::XS->new->incr_parse ("[5][7][1,2]"); |
|
|
760 | |
750 | =item $lvalue_string = $json->incr_text |
761 | =item $lvalue_string = $json->incr_text |
751 | |
762 | |
752 | This method returns the currently stored JSON fragment as an lvalue, that |
763 | This method returns the currently stored JSON fragment as an lvalue, that |
753 | is, you can manipulate it. This I<only> works when a preceding call to |
764 | is, you can manipulate it. This I<only> works when a preceding call to |
754 | C<incr_parse> in I<scalar context> successfully returned an object. Under |
765 | C<incr_parse> in I<scalar context> successfully returned an object. Under |
… | |
… | |
761 | JSON object or b) parsing multiple JSON objects separated by non-JSON text |
772 | JSON object or b) parsing multiple JSON objects separated by non-JSON text |
762 | (such as commas). |
773 | (such as commas). |
763 | |
774 | |
764 | =item $json->incr_skip |
775 | =item $json->incr_skip |
765 | |
776 | |
766 | This will reset the state of the incremental parser and will remove the |
777 | This will reset the state of the incremental parser and will remove |
767 | parsed text from the input buffer. This is useful after C<incr_parse> |
778 | the parsed text from the input buffer so far. This is useful after |
768 | died, in which case the input buffer and incremental parser state is left |
779 | C<incr_parse> died, in which case the input buffer and incremental parser |
769 | unchanged, to skip the text parsed so far and to reset the parse state. |
780 | state is left unchanged, to skip the text parsed so far and to reset the |
|
|
781 | parse state. |
|
|
782 | |
|
|
783 | The difference to C<incr_reset> is that only text until the parse error |
|
|
784 | occured is removed. |
|
|
785 | |
|
|
786 | =item $json->incr_reset |
|
|
787 | |
|
|
788 | This completely resets the incremental parser, that is, after this call, |
|
|
789 | it will be as if the parser had never parsed anything. |
|
|
790 | |
|
|
791 | This is useful if you want to repeatedly parse JSON objects and want to |
|
|
792 | ignore any trailing data, which means you have to reset the parser after |
|
|
793 | each successful decode. |
770 | |
794 | |
771 | =back |
795 | =back |
772 | |
796 | |
773 | =head2 LIMITATIONS |
797 | =head2 LIMITATIONS |
774 | |
798 | |
… | |
… | |
970 | Numbers containing a fractional or exponential part will always be |
994 | Numbers containing a fractional or exponential part will always be |
971 | represented as numeric (floating point) values, possibly at a loss of |
995 | represented as numeric (floating point) values, possibly at a loss of |
972 | precision (in which case you might lose perfect roundtripping ability, but |
996 | precision (in which case you might lose perfect roundtripping ability, but |
973 | the JSON number will still be re-encoded as a JSON number). |
997 | the JSON number will still be re-encoded as a JSON number). |
974 | |
998 | |
|
|
999 | Note that precision is not accuracy - binary floating point values cannot |
|
|
1000 | represent most decimal fractions exactly, and when converting from and to |
|
|
1001 | floating point, JSON::XS only guarantees precision up to but not including |
|
|
1002 | the leats significant bit. |
|
|
1003 | |
975 | =item true, false |
1004 | =item true, false |
976 | |
1005 | |
977 | These JSON atoms become C<JSON::XS::true> and C<JSON::XS::false>, |
1006 | These JSON atoms become C<JSON::XS::true> and C<JSON::XS::false>, |
978 | respectively. They are overloaded to act almost exactly like the numbers |
1007 | respectively. They are overloaded to act almost exactly like the numbers |
979 | C<1> and C<0>. You can check whether a scalar is a JSON boolean by using |
1008 | C<1> and C<0>. You can check whether a scalar is a JSON boolean by using |
… | |
… | |
1015 | Other unblessed references are generally not allowed and will cause an |
1044 | Other unblessed references are generally not allowed and will cause an |
1016 | exception to be thrown, except for references to the integers C<0> and |
1045 | exception to be thrown, except for references to the integers C<0> and |
1017 | C<1>, which get turned into C<false> and C<true> atoms in JSON. You can |
1046 | C<1>, which get turned into C<false> and C<true> atoms in JSON. You can |
1018 | also use C<JSON::XS::false> and C<JSON::XS::true> to improve readability. |
1047 | also use C<JSON::XS::false> and C<JSON::XS::true> to improve readability. |
1019 | |
1048 | |
1020 | encode_json [\0,JSON::XS::true] # yields [false,true] |
1049 | encode_json [\0, JSON::XS::true] # yields [false,true] |
1021 | |
1050 | |
1022 | =item JSON::XS::true, JSON::XS::false |
1051 | =item JSON::XS::true, JSON::XS::false |
1023 | |
1052 | |
1024 | These special values become JSON true and JSON false values, |
1053 | These special values become JSON true and JSON false values, |
1025 | respectively. You can also use C<\1> and C<\0> directly if you want. |
1054 | respectively. You can also use C<\1> and C<\0> directly if you want. |
… | |
… | |
1065 | $x *= 1; # same thing, the choice is yours. |
1094 | $x *= 1; # same thing, the choice is yours. |
1066 | |
1095 | |
1067 | You can not currently force the type in other, less obscure, ways. Tell me |
1096 | You can not currently force the type in other, less obscure, ways. Tell me |
1068 | if you need this capability (but don't forget to explain why it's needed |
1097 | if you need this capability (but don't forget to explain why it's needed |
1069 | :). |
1098 | :). |
|
|
1099 | |
|
|
1100 | Note that numerical precision has the same meaning as under Perl (so |
|
|
1101 | binary to decimal conversion follows the same rules as in Perl, which |
|
|
1102 | can differ to other languages). Also, your perl interpreter might expose |
|
|
1103 | extensions to the floating point numbers of your platform, such as |
|
|
1104 | infinities or NaN's - these cannot be represented in JSON, and it is an |
|
|
1105 | error to pass those in. |
1070 | |
1106 | |
1071 | =back |
1107 | =back |
1072 | |
1108 | |
1073 | |
1109 | |
1074 | =head1 ENCODING/CODESET FLAG NOTES |
1110 | =head1 ENCODING/CODESET FLAG NOTES |
… | |
… | |
1167 | proper subset of most 8-bit and multibyte encodings in use in the world. |
1203 | proper subset of most 8-bit and multibyte encodings in use in the world. |
1168 | |
1204 | |
1169 | =back |
1205 | =back |
1170 | |
1206 | |
1171 | |
1207 | |
|
|
1208 | =head2 JSON and ECMAscript |
|
|
1209 | |
|
|
1210 | JSON syntax is based on how literals are represented in javascript (the |
|
|
1211 | not-standardised predecessor of ECMAscript) which is presumably why it is |
|
|
1212 | called "JavaScript Object Notation". |
|
|
1213 | |
|
|
1214 | However, JSON is not a subset (and also not a superset of course) of |
|
|
1215 | ECMAscript (the standard) or javascript (whatever browsers actually |
|
|
1216 | implement). |
|
|
1217 | |
|
|
1218 | If you want to use javascript's C<eval> function to "parse" JSON, you |
|
|
1219 | might run into parse errors for valid JSON texts, or the resulting data |
|
|
1220 | structure might not be queryable: |
|
|
1221 | |
|
|
1222 | One of the problems is that U+2028 and U+2029 are valid characters inside |
|
|
1223 | JSON strings, but are not allowed in ECMAscript string literals, so the |
|
|
1224 | following Perl fragment will not output something that can be guaranteed |
|
|
1225 | to be parsable by javascript's C<eval>: |
|
|
1226 | |
|
|
1227 | use JSON::XS; |
|
|
1228 | |
|
|
1229 | print encode_json [chr 0x2028]; |
|
|
1230 | |
|
|
1231 | The right fix for this is to use a proper JSON parser in your javascript |
|
|
1232 | programs, and not rely on C<eval> (see for example Douglas Crockford's |
|
|
1233 | F<json2.js> parser). |
|
|
1234 | |
|
|
1235 | If this is not an option, you can, as a stop-gap measure, simply encode to |
|
|
1236 | ASCII-only JSON: |
|
|
1237 | |
|
|
1238 | use JSON::XS; |
|
|
1239 | |
|
|
1240 | print JSON::XS->new->ascii->encode ([chr 0x2028]); |
|
|
1241 | |
|
|
1242 | Note that this will enlarge the resulting JSON text quite a bit if you |
|
|
1243 | have many non-ASCII characters. You might be tempted to run some regexes |
|
|
1244 | to only escape U+2028 and U+2029, e.g.: |
|
|
1245 | |
|
|
1246 | # DO NOT USE THIS! |
|
|
1247 | my $json = JSON::XS->new->utf8->encode ([chr 0x2028]); |
|
|
1248 | $json =~ s/\xe2\x80\xa8/\\u2028/g; # escape U+2028 |
|
|
1249 | $json =~ s/\xe2\x80\xa9/\\u2029/g; # escape U+2029 |
|
|
1250 | print $json; |
|
|
1251 | |
|
|
1252 | Note that I<this is a bad idea>: the above only works for U+2028 and |
|
|
1253 | U+2029 and thus only for fully ECMAscript-compliant parsers. Many existing |
|
|
1254 | javascript implementations, however, have issues with other characters as |
|
|
1255 | well - using C<eval> naively simply I<will> cause problems. |
|
|
1256 | |
|
|
1257 | Another problem is that some javascript implementations reserve |
|
|
1258 | some property names for their own purposes (which probably makes |
|
|
1259 | them non-ECMAscript-compliant). For example, Iceweasel reserves the |
|
|
1260 | C<__proto__> property name for it's own purposes. |
|
|
1261 | |
|
|
1262 | If that is a problem, you could parse try to filter the resulting JSON |
|
|
1263 | output for these property strings, e.g.: |
|
|
1264 | |
|
|
1265 | $json =~ s/"__proto__"\s*:/"__proto__renamed":/g; |
|
|
1266 | |
|
|
1267 | This works because C<__proto__> is not valid outside of strings, so every |
|
|
1268 | occurence of C<"__proto__"\s*:> must be a string used as property name. |
|
|
1269 | |
|
|
1270 | If you know of other incompatibilities, please let me know. |
|
|
1271 | |
|
|
1272 | |
1172 | =head2 JSON and YAML |
1273 | =head2 JSON and YAML |
1173 | |
1274 | |
1174 | You often hear that JSON is a subset of YAML. This is, however, a mass |
1275 | You often hear that JSON is a subset of YAML. This is, however, a mass |
1175 | hysteria(*) and very far from the truth (as of the time of this writing), |
1276 | hysteria(*) and very far from the truth (as of the time of this writing), |
1176 | so let me state it clearly: I<in general, there is no way to configure |
1277 | so let me state it clearly: I<in general, there is no way to configure |
… | |
… | |
1184 | my $yaml = $to_yaml->encode ($ref) . "\n"; |
1285 | my $yaml = $to_yaml->encode ($ref) . "\n"; |
1185 | |
1286 | |
1186 | This will I<usually> generate JSON texts that also parse as valid |
1287 | This will I<usually> generate JSON texts that also parse as valid |
1187 | YAML. Please note that YAML has hardcoded limits on (simple) object key |
1288 | YAML. Please note that YAML has hardcoded limits on (simple) object key |
1188 | lengths that JSON doesn't have and also has different and incompatible |
1289 | lengths that JSON doesn't have and also has different and incompatible |
1189 | unicode handling, so you should make sure that your hash keys are |
1290 | unicode character escape syntax, so you should make sure that your hash |
1190 | noticeably shorter than the 1024 "stream characters" YAML allows and that |
1291 | keys are noticeably shorter than the 1024 "stream characters" YAML allows |
1191 | you do not have characters with codepoint values outside the Unicode BMP |
1292 | and that you do not have characters with codepoint values outside the |
1192 | (basic multilingual page). YAML also does not allow C<\/> sequences in |
1293 | Unicode BMP (basic multilingual page). YAML also does not allow C<\/> |
1193 | strings (which JSON::XS does not I<currently> generate, but other JSON |
1294 | sequences in strings (which JSON::XS does not I<currently> generate, but |
1194 | generators might). |
1295 | other JSON generators might). |
1195 | |
1296 | |
1196 | There might be other incompatibilities that I am not aware of (or the YAML |
1297 | There might be other incompatibilities that I am not aware of (or the YAML |
1197 | specification has been changed yet again - it does so quite often). In |
1298 | specification has been changed yet again - it does so quite often). In |
1198 | general you should not try to generate YAML with a JSON generator or vice |
1299 | general you should not try to generate YAML with a JSON generator or vice |
1199 | versa, or try to parse JSON with a YAML parser or vice versa: chances are |
1300 | versa, or try to parse JSON with a YAML parser or vice versa: chances are |
… | |
… | |
1218 | that difficult or long) and finally make YAML compatible to it, and |
1319 | that difficult or long) and finally make YAML compatible to it, and |
1219 | educating users about the changes, instead of spreading lies about the |
1320 | educating users about the changes, instead of spreading lies about the |
1220 | real compatibility for many I<years> and trying to silence people who |
1321 | real compatibility for many I<years> and trying to silence people who |
1221 | point out that it isn't true. |
1322 | point out that it isn't true. |
1222 | |
1323 | |
|
|
1324 | Addendum/2009: the YAML 1.2 spec is still incomaptible with JSON, even |
|
|
1325 | though the incompatibilities have been documented (and are known to |
|
|
1326 | Brian) for many years and the spec makes explicit claims that YAML is a |
|
|
1327 | superset of JSON. It would be so easy to fix, but apparently, bullying and |
|
|
1328 | corrupting userdata is so much easier. |
|
|
1329 | |
1223 | =back |
1330 | =back |
1224 | |
1331 | |
1225 | |
1332 | |
1226 | =head2 SPEED |
1333 | =head2 SPEED |
1227 | |
1334 | |
… | |
… | |
1234 | a very short single-line JSON string (also available at |
1341 | a very short single-line JSON string (also available at |
1235 | L<http://dist.schmorp.de/misc/json/short.json>). |
1342 | L<http://dist.schmorp.de/misc/json/short.json>). |
1236 | |
1343 | |
1237 | {"method": "handleMessage", "params": ["user1", |
1344 | {"method": "handleMessage", "params": ["user1", |
1238 | "we were just talking"], "id": null, "array":[1,11,234,-5,1e5,1e7, |
1345 | "we were just talking"], "id": null, "array":[1,11,234,-5,1e5,1e7, |
1239 | true, false]} |
1346 | 1, 0]} |
1240 | |
1347 | |
1241 | It shows the number of encodes/decodes per second (JSON::XS uses |
1348 | It shows the number of encodes/decodes per second (JSON::XS uses |
1242 | the functional interface, while JSON::XS/2 uses the OO interface |
1349 | the functional interface, while JSON::XS/2 uses the OO interface |
1243 | with pretty-printing and hashkey sorting enabled, JSON::XS/3 enables |
1350 | with pretty-printing and hashkey sorting enabled, JSON::XS/3 enables |
1244 | shrink). Higher is better: |
1351 | shrink. JSON::DWIW/DS uses the deserialise function, while JSON::DWIW::FJ |
|
|
1352 | uses the from_json method). Higher is better: |
1245 | |
1353 | |
1246 | module | encode | decode | |
1354 | module | encode | decode | |
1247 | -----------|------------|------------| |
1355 | --------------|------------|------------| |
1248 | JSON 1.x | 4990.842 | 4088.813 | |
1356 | JSON::DWIW/DS | 86302.551 | 102300.098 | |
1249 | JSON::DWIW | 51653.990 | 71575.154 | |
1357 | JSON::DWIW/FJ | 86302.551 | 75983.768 | |
1250 | JSON::PC | 65948.176 | 74631.744 | |
1358 | JSON::PP | 15827.562 | 6638.658 | |
1251 | JSON::PP | 8931.652 | 3817.168 | |
1359 | JSON::Syck | 63358.066 | 47662.545 | |
1252 | JSON::Syck | 24877.248 | 27776.848 | |
1360 | JSON::XS | 511500.488 | 511500.488 | |
1253 | JSON::XS | 388361.481 | 227951.304 | |
1361 | JSON::XS/2 | 291271.111 | 388361.481 | |
1254 | JSON::XS/2 | 227951.304 | 218453.333 | |
1362 | JSON::XS/3 | 361577.931 | 361577.931 | |
1255 | JSON::XS/3 | 338250.323 | 218453.333 | |
1363 | Storable | 66788.280 | 265462.278 | |
1256 | Storable | 16500.016 | 135300.129 | |
|
|
1257 | -----------+------------+------------+ |
1364 | --------------+------------+------------+ |
1258 | |
1365 | |
1259 | That is, JSON::XS is about five times faster than JSON::DWIW on encoding, |
1366 | That is, JSON::XS is almost six times faster than JSON::DWIW on encoding, |
1260 | about three times faster on decoding, and over forty times faster |
1367 | about five times faster on decoding, and over thirty to seventy times |
1261 | than JSON, even with pretty-printing and key sorting. It also compares |
1368 | faster than JSON's pure perl implementation. It also compares favourably |
1262 | favourably to Storable for small amounts of data. |
1369 | to Storable for small amounts of data. |
1263 | |
1370 | |
1264 | Using a longer test string (roughly 18KB, generated from Yahoo! Locals |
1371 | Using a longer test string (roughly 18KB, generated from Yahoo! Locals |
1265 | search API (L<http://dist.schmorp.de/misc/json/long.json>). |
1372 | search API (L<http://dist.schmorp.de/misc/json/long.json>). |
1266 | |
1373 | |
1267 | module | encode | decode | |
1374 | module | encode | decode | |
1268 | -----------|------------|------------| |
1375 | --------------|------------|------------| |
1269 | JSON 1.x | 55.260 | 34.971 | |
1376 | JSON::DWIW/DS | 1647.927 | 2673.916 | |
1270 | JSON::DWIW | 825.228 | 1082.513 | |
1377 | JSON::DWIW/FJ | 1630.249 | 2596.128 | |
1271 | JSON::PC | 3571.444 | 2394.829 | |
|
|
1272 | JSON::PP | 210.987 | 32.574 | |
1378 | JSON::PP | 400.640 | 62.311 | |
1273 | JSON::Syck | 552.551 | 787.544 | |
1379 | JSON::Syck | 1481.040 | 1524.869 | |
1274 | JSON::XS | 5780.463 | 4854.519 | |
1380 | JSON::XS | 20661.596 | 9541.183 | |
1275 | JSON::XS/2 | 3869.998 | 4798.975 | |
1381 | JSON::XS/2 | 10683.403 | 9416.938 | |
1276 | JSON::XS/3 | 5862.880 | 4798.975 | |
1382 | JSON::XS/3 | 20661.596 | 9400.054 | |
1277 | Storable | 4445.002 | 5235.027 | |
1383 | Storable | 19765.806 | 10000.725 | |
1278 | -----------+------------+------------+ |
1384 | --------------+------------+------------+ |
1279 | |
1385 | |
1280 | Again, JSON::XS leads by far (except for Storable which non-surprisingly |
1386 | Again, JSON::XS leads by far (except for Storable which non-surprisingly |
1281 | decodes faster). |
1387 | decodes a bit faster). |
1282 | |
1388 | |
1283 | On large strings containing lots of high Unicode characters, some modules |
1389 | On large strings containing lots of high Unicode characters, some modules |
1284 | (such as JSON::PC) seem to decode faster than JSON::XS, but the result |
1390 | (such as JSON::PC) seem to decode faster than JSON::XS, but the result |
1285 | will be broken due to missing (or wrong) Unicode handling. Others refuse |
1391 | will be broken due to missing (or wrong) Unicode handling. Others refuse |
1286 | to decode or encode properly, so it was impossible to prepare a fair |
1392 | to decode or encode properly, so it was impossible to prepare a fair |
… | |
… | |
1322 | information you might want to make sure that exceptions thrown by JSON::XS |
1428 | information you might want to make sure that exceptions thrown by JSON::XS |
1323 | will not end up in front of untrusted eyes. |
1429 | will not end up in front of untrusted eyes. |
1324 | |
1430 | |
1325 | If you are using JSON::XS to return packets to consumption |
1431 | If you are using JSON::XS to return packets to consumption |
1326 | by JavaScript scripts in a browser you should have a look at |
1432 | by JavaScript scripts in a browser you should have a look at |
1327 | L<http://jpsykes.com/47/practical-csrf-and-json-security> to see whether |
1433 | L<http://blog.archive.jpsykes.com/47/practical-csrf-and-json-security/> to |
1328 | you are vulnerable to some common attack vectors (which really are browser |
1434 | see whether you are vulnerable to some common attack vectors (which really |
1329 | design bugs, but it is still you who will have to deal with it, as major |
1435 | are browser design bugs, but it is still you who will have to deal with |
1330 | browser developers care only for features, not about getting security |
1436 | it, as major browser developers care only for features, not about getting |
1331 | right). |
1437 | security right). |
1332 | |
1438 | |
1333 | |
1439 | |
1334 | =head1 THREADS |
1440 | =head1 THREADS |
1335 | |
1441 | |
1336 | This module is I<not> guaranteed to be thread safe and there are no |
1442 | This module is I<not> guaranteed to be thread safe and there are no |