… | |
… | |
64 | so, and even documents what "correct" means. |
64 | so, and even documents what "correct" means. |
65 | |
65 | |
66 | =item * round-trip integrity |
66 | =item * round-trip integrity |
67 | |
67 | |
68 | When you serialise a perl data structure using only data types supported |
68 | When you serialise a perl data structure using only data types supported |
69 | 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 |
70 | (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 |
71 | 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 |
72 | section below to learn about those. |
72 | MAPPING section below to learn about those. |
73 | |
73 | |
74 | =item * strict checking of JSON correctness |
74 | =item * strict checking of JSON correctness |
75 | |
75 | |
76 | 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, |
77 | 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 |
… | |
… | |
83 | this module usually compares favourably in terms of speed, too. |
83 | this module usually compares favourably in terms of speed, too. |
84 | |
84 | |
85 | =item * simple to use |
85 | =item * simple to use |
86 | |
86 | |
87 | This module has both a simple functional interface as well as an object |
87 | This module has both a simple functional interface as well as an object |
88 | oriented interface interface. |
88 | oriented interface. |
89 | |
89 | |
90 | =item * reasonably versatile output formats |
90 | =item * reasonably versatile output formats |
91 | |
91 | |
92 | You can choose between the most compact guaranteed-single-line format |
92 | You can choose between the most compact guaranteed-single-line format |
93 | possible (nice for simple line-based protocols), a pure-ASCII format |
93 | possible (nice for simple line-based protocols), a pure-ASCII format |
… | |
… | |
99 | |
99 | |
100 | =cut |
100 | =cut |
101 | |
101 | |
102 | package JSON::XS; |
102 | package JSON::XS; |
103 | |
103 | |
104 | no warnings; |
104 | use common::sense; |
105 | use strict; |
|
|
106 | |
105 | |
107 | our $VERSION = '2.232'; |
106 | our $VERSION = 2.34; |
108 | our @ISA = qw(Exporter); |
107 | our @ISA = qw(Exporter); |
109 | |
108 | |
110 | our @EXPORT = qw(encode_json decode_json to_json from_json); |
109 | our @EXPORT = qw(encode_json decode_json to_json from_json); |
111 | |
110 | |
112 | sub to_json($) { |
111 | sub to_json($) { |
… | |
… | |
433 | If C<$enable> is true (or missing), then the C<encode> method will output JSON objects |
432 | If C<$enable> is true (or missing), then the C<encode> method will output JSON objects |
434 | by sorting their keys. This is adding a comparatively high overhead. |
433 | by sorting their keys. This is adding a comparatively high overhead. |
435 | |
434 | |
436 | If C<$enable> is false, then the C<encode> method will output key-value |
435 | If C<$enable> is false, then the C<encode> method will output key-value |
437 | pairs in the order Perl stores them (which will likely change between runs |
436 | pairs in the order Perl stores them (which will likely change between runs |
438 | of the same script). |
437 | of the same script, and can change even within the same run from 5.18 |
|
|
438 | onwards). |
439 | |
439 | |
440 | This option is useful if you want the same data structure to be encoded as |
440 | This option is useful if you want the same data structure to be encoded as |
441 | the same JSON text (given the same overall settings). If it is disabled, |
441 | the same JSON text (given the same overall settings). If it is disabled, |
442 | the same hash might be encoded differently even if contains the same data, |
442 | the same hash might be encoded differently even if contains the same data, |
443 | as key-value pairs have no inherent ordering in Perl. |
443 | as key-value pairs have no inherent ordering in Perl. |
444 | |
444 | |
445 | This setting has no effect when decoding JSON texts. |
445 | This setting has no effect when decoding JSON texts. |
|
|
446 | |
|
|
447 | This setting has currently no effect on tied hashes. |
446 | |
448 | |
447 | =item $json = $json->allow_nonref ([$enable]) |
449 | =item $json = $json->allow_nonref ([$enable]) |
448 | |
450 | |
449 | =item $enabled = $json->get_allow_nonref |
451 | =item $enabled = $json->get_allow_nonref |
450 | |
452 | |
… | |
… | |
712 | calls). |
714 | calls). |
713 | |
715 | |
714 | JSON::XS will only attempt to parse the JSON text once it is sure it |
716 | JSON::XS will only attempt to parse the JSON text once it is sure it |
715 | has enough text to get a decisive result, using a very simple but |
717 | has enough text to get a decisive result, using a very simple but |
716 | truly incremental parser. This means that it sometimes won't stop as |
718 | truly incremental parser. This means that it sometimes won't stop as |
717 | early as the full parser, for example, it doesn't detect parenthese |
719 | early as the full parser, for example, it doesn't detect mismatched |
718 | mismatches. The only thing it guarantees is that it starts decoding as |
720 | parentheses. The only thing it guarantees is that it starts decoding as |
719 | soon as a syntactically valid JSON text has been seen. This means you need |
721 | soon as a syntactically valid JSON text has been seen. This means you need |
720 | to set resource limits (e.g. C<max_size>) to ensure the parser will stop |
722 | to set resource limits (e.g. C<max_size>) to ensure the parser will stop |
721 | parsing in the presence if syntax errors. |
723 | parsing in the presence if syntax errors. |
722 | |
724 | |
723 | The following methods implement this incremental parser. |
725 | The following methods implement this incremental parser. |
… | |
… | |
739 | |
741 | |
740 | If the method is called in scalar context, then it will try to extract |
742 | If the method is called in scalar context, then it will try to extract |
741 | exactly I<one> JSON object. If that is successful, it will return this |
743 | exactly I<one> JSON object. If that is successful, it will return this |
742 | object, otherwise it will return C<undef>. If there is a parse error, |
744 | object, otherwise it will return C<undef>. If there is a parse error, |
743 | this method will croak just as C<decode> would do (one can then use |
745 | this method will croak just as C<decode> would do (one can then use |
744 | C<incr_skip> to skip the errornous part). This is the most common way of |
746 | C<incr_skip> to skip the erroneous part). This is the most common way of |
745 | using the method. |
747 | using the method. |
746 | |
748 | |
747 | And finally, in list context, it will try to extract as many objects |
749 | And finally, in list context, it will try to extract as many objects |
748 | from the stream as it can find and return them, or the empty list |
750 | from the stream as it can find and return them, or the empty list |
749 | otherwise. For this to work, there must be no separators between the JSON |
751 | otherwise. For this to work, there must be no separators between the JSON |
750 | objects or arrays, instead they must be concatenated back-to-back. If |
752 | objects or arrays, instead they must be concatenated back-to-back. If |
751 | an error occurs, an exception will be raised as in the scalar context |
753 | an error occurs, an exception will be raised as in the scalar context |
752 | case. Note that in this case, any previously-parsed JSON texts will be |
754 | case. Note that in this case, any previously-parsed JSON texts will be |
753 | lost. |
755 | lost. |
754 | |
756 | |
|
|
757 | Example: Parse some JSON arrays/objects in a given string and return |
|
|
758 | them. |
|
|
759 | |
|
|
760 | my @objs = JSON::XS->new->incr_parse ("[5][7][1,2]"); |
|
|
761 | |
755 | =item $lvalue_string = $json->incr_text |
762 | =item $lvalue_string = $json->incr_text |
756 | |
763 | |
757 | This method returns the currently stored JSON fragment as an lvalue, that |
764 | This method returns the currently stored JSON fragment as an lvalue, that |
758 | is, you can manipulate it. This I<only> works when a preceding call to |
765 | is, you can manipulate it. This I<only> works when a preceding call to |
759 | C<incr_parse> in I<scalar context> successfully returned an object. Under |
766 | C<incr_parse> in I<scalar context> successfully returned an object. Under |
… | |
… | |
773 | C<incr_parse> died, in which case the input buffer and incremental parser |
780 | C<incr_parse> died, in which case the input buffer and incremental parser |
774 | state is left unchanged, to skip the text parsed so far and to reset the |
781 | state is left unchanged, to skip the text parsed so far and to reset the |
775 | parse state. |
782 | parse state. |
776 | |
783 | |
777 | The difference to C<incr_reset> is that only text until the parse error |
784 | The difference to C<incr_reset> is that only text until the parse error |
778 | occured is removed. |
785 | occurred is removed. |
779 | |
786 | |
780 | =item $json->incr_reset |
787 | =item $json->incr_reset |
781 | |
788 | |
782 | This completely resets the incremental parser, that is, after this call, |
789 | This completely resets the incremental parser, that is, after this call, |
783 | it will be as if the parser had never parsed anything. |
790 | it will be as if the parser had never parsed anything. |
… | |
… | |
981 | If the number consists of digits only, JSON::XS will try to represent |
988 | If the number consists of digits only, JSON::XS will try to represent |
982 | it as an integer value. If that fails, it will try to represent it as |
989 | it as an integer value. If that fails, it will try to represent it as |
983 | a numeric (floating point) value if that is possible without loss of |
990 | a numeric (floating point) value if that is possible without loss of |
984 | precision. Otherwise it will preserve the number as a string value (in |
991 | precision. Otherwise it will preserve the number as a string value (in |
985 | which case you lose roundtripping ability, as the JSON number will be |
992 | which case you lose roundtripping ability, as the JSON number will be |
986 | re-encoded toa JSON string). |
993 | re-encoded to a JSON string). |
987 | |
994 | |
988 | Numbers containing a fractional or exponential part will always be |
995 | Numbers containing a fractional or exponential part will always be |
989 | represented as numeric (floating point) values, possibly at a loss of |
996 | represented as numeric (floating point) values, possibly at a loss of |
990 | precision (in which case you might lose perfect roundtripping ability, but |
997 | precision (in which case you might lose perfect roundtripping ability, but |
991 | the JSON number will still be re-encoded as a JSON number). |
998 | the JSON number will still be re-encoded as a JSON number). |
|
|
999 | |
|
|
1000 | Note that precision is not accuracy - binary floating point values cannot |
|
|
1001 | represent most decimal fractions exactly, and when converting from and to |
|
|
1002 | floating point, JSON::XS only guarantees precision up to but not including |
|
|
1003 | the least significant bit. |
992 | |
1004 | |
993 | =item true, false |
1005 | =item true, false |
994 | |
1006 | |
995 | These JSON atoms become C<JSON::XS::true> and C<JSON::XS::false>, |
1007 | These JSON atoms become C<JSON::XS::true> and C<JSON::XS::false>, |
996 | respectively. They are overloaded to act almost exactly like the numbers |
1008 | respectively. They are overloaded to act almost exactly like the numbers |
… | |
… | |
1084 | |
1096 | |
1085 | You can not currently force the type in other, less obscure, ways. Tell me |
1097 | You can not currently force the type in other, less obscure, ways. Tell me |
1086 | if you need this capability (but don't forget to explain why it's needed |
1098 | if you need this capability (but don't forget to explain why it's needed |
1087 | :). |
1099 | :). |
1088 | |
1100 | |
|
|
1101 | Note that numerical precision has the same meaning as under Perl (so |
|
|
1102 | binary to decimal conversion follows the same rules as in Perl, which |
|
|
1103 | can differ to other languages). Also, your perl interpreter might expose |
|
|
1104 | extensions to the floating point numbers of your platform, such as |
|
|
1105 | infinities or NaN's - these cannot be represented in JSON, and it is an |
|
|
1106 | error to pass those in. |
|
|
1107 | |
1089 | =back |
1108 | =back |
1090 | |
1109 | |
1091 | |
1110 | |
1092 | =head1 ENCODING/CODESET FLAG NOTES |
1111 | =head1 ENCODING/CODESET FLAG NOTES |
1093 | |
1112 | |
… | |
… | |
1119 | =item C<utf8> flag disabled |
1138 | =item C<utf8> flag disabled |
1120 | |
1139 | |
1121 | When C<utf8> is disabled (the default), then C<encode>/C<decode> generate |
1140 | When C<utf8> is disabled (the default), then C<encode>/C<decode> generate |
1122 | and expect Unicode strings, that is, characters with high ordinal Unicode |
1141 | and expect Unicode strings, that is, characters with high ordinal Unicode |
1123 | values (> 255) will be encoded as such characters, and likewise such |
1142 | values (> 255) will be encoded as such characters, and likewise such |
1124 | characters are decoded as-is, no canges to them will be done, except |
1143 | characters are decoded as-is, no changes to them will be done, except |
1125 | "(re-)interpreting" them as Unicode codepoints or Unicode characters, |
1144 | "(re-)interpreting" them as Unicode codepoints or Unicode characters, |
1126 | respectively (to Perl, these are the same thing in strings unless you do |
1145 | respectively (to Perl, these are the same thing in strings unless you do |
1127 | funny/weird/dumb stuff). |
1146 | funny/weird/dumb stuff). |
1128 | |
1147 | |
1129 | This is useful when you want to do the encoding yourself (e.g. when you |
1148 | This is useful when you want to do the encoding yourself (e.g. when you |
… | |
… | |
1209 | use JSON::XS; |
1228 | use JSON::XS; |
1210 | |
1229 | |
1211 | print encode_json [chr 0x2028]; |
1230 | print encode_json [chr 0x2028]; |
1212 | |
1231 | |
1213 | The right fix for this is to use a proper JSON parser in your javascript |
1232 | The right fix for this is to use a proper JSON parser in your javascript |
1214 | programs, and not rely on C<eval>. |
1233 | programs, and not rely on C<eval> (see for example Douglas Crockford's |
|
|
1234 | F<json2.js> parser). |
1215 | |
1235 | |
1216 | If this is not an option, you can, as a stop-gap measure, simply encode to |
1236 | If this is not an option, you can, as a stop-gap measure, simply encode to |
1217 | ASCII-only JSON: |
1237 | ASCII-only JSON: |
1218 | |
1238 | |
1219 | use JSON::XS; |
1239 | use JSON::XS; |
1220 | |
1240 | |
1221 | print JSON::XS->new->ascii->encode ([chr 0x2028]); |
1241 | print JSON::XS->new->ascii->encode ([chr 0x2028]); |
1222 | |
1242 | |
1223 | And if you are concerned about the size of the resulting JSON text, you |
1243 | Note that this will enlarge the resulting JSON text quite a bit if you |
1224 | can run some regexes to only escape U+2028 and U+2029: |
1244 | have many non-ASCII characters. You might be tempted to run some regexes |
|
|
1245 | to only escape U+2028 and U+2029, e.g.: |
1225 | |
1246 | |
1226 | use JSON::XS; |
1247 | # DO NOT USE THIS! |
1227 | |
|
|
1228 | my $json = JSON::XS->new->utf8->encode ([chr 0x2028]); |
1248 | my $json = JSON::XS->new->utf8->encode ([chr 0x2028]); |
1229 | $json =~ s/\xe2\x80\xa8/\\u2028/g; # escape U+2028 |
1249 | $json =~ s/\xe2\x80\xa8/\\u2028/g; # escape U+2028 |
1230 | $json =~ s/\xe2\x80\xa9/\\u2029/g; # escape U+2029 |
1250 | $json =~ s/\xe2\x80\xa9/\\u2029/g; # escape U+2029 |
1231 | print $json; |
1251 | print $json; |
1232 | |
1252 | |
1233 | This works because U+2028/U+2029 are not allowed outside of strings and |
1253 | Note that I<this is a bad idea>: the above only works for U+2028 and |
1234 | are not used for syntax, so replacing them unconditionally just works. |
|
|
1235 | |
|
|
1236 | Note, however, that fixing the broken JSON parser is better than working |
|
|
1237 | around it in every other generator. The above regexes should work well in |
|
|
1238 | other languages, as long as they operate on UTF-8. It is equally valid to |
|
|
1239 | replace all occurences of U+2028/2029 directly by their \\u-escaped forms |
|
|
1240 | in unicode texts, so they can simply be used to fix any parsers relying on |
|
|
1241 | C<eval> by first applying the regexes on the encoded texts. |
|
|
1242 | |
|
|
1243 | Note also that the above only works for U+2028 and U+2029 and thus |
|
|
1244 | only for fully ECMAscript-compliant parsers. Many existing javascript |
1254 | U+2029 and thus only for fully ECMAscript-compliant parsers. Many existing |
1245 | implementations misparse other characters as well. Best rely on a good |
1255 | javascript implementations, however, have issues with other characters as |
1246 | JSON parser, such as Douglas Crockfords F<json2.js>, which escapes the |
1256 | well - using C<eval> naively simply I<will> cause problems. |
1247 | above and many more problematic characters properly before passing them |
|
|
1248 | into C<eval>. |
|
|
1249 | |
1257 | |
1250 | Another problem is that some javascript implementations reserve |
1258 | Another problem is that some javascript implementations reserve |
1251 | some property names for their own purposes (which probably makes |
1259 | some property names for their own purposes (which probably makes |
1252 | them non-ECMAscript-compliant). For example, Iceweasel reserves the |
1260 | them non-ECMAscript-compliant). For example, Iceweasel reserves the |
1253 | C<__proto__> property name for it's own purposes. |
1261 | C<__proto__> property name for its own purposes. |
1254 | |
1262 | |
1255 | If that is a problem, you could parse try to filter the resulting JSON |
1263 | If that is a problem, you could parse try to filter the resulting JSON |
1256 | output for these property strings, e.g.: |
1264 | output for these property strings, e.g.: |
1257 | |
1265 | |
1258 | $json =~ s/"__proto__"\s*:/"__proto__renamed":/g; |
1266 | $json =~ s/"__proto__"\s*:/"__proto__renamed":/g; |
1259 | |
1267 | |
1260 | This works because C<__proto__> is not valid outside of strings, so every |
1268 | This works because C<__proto__> is not valid outside of strings, so every |
1261 | occurence of C<"__proto__"\s*:> must be a string used as property name. |
1269 | occurrence of C<"__proto__"\s*:> must be a string used as property name. |
1262 | |
1270 | |
1263 | If you know of other incompatibilities, please let me know. |
1271 | If you know of other incompatibilities, please let me know. |
1264 | |
1272 | |
1265 | |
1273 | |
1266 | =head2 JSON and YAML |
1274 | =head2 JSON and YAML |
… | |
… | |
1278 | my $yaml = $to_yaml->encode ($ref) . "\n"; |
1286 | my $yaml = $to_yaml->encode ($ref) . "\n"; |
1279 | |
1287 | |
1280 | This will I<usually> generate JSON texts that also parse as valid |
1288 | This will I<usually> generate JSON texts that also parse as valid |
1281 | YAML. Please note that YAML has hardcoded limits on (simple) object key |
1289 | YAML. Please note that YAML has hardcoded limits on (simple) object key |
1282 | lengths that JSON doesn't have and also has different and incompatible |
1290 | lengths that JSON doesn't have and also has different and incompatible |
1283 | unicode handling, so you should make sure that your hash keys are |
1291 | unicode character escape syntax, so you should make sure that your hash |
1284 | noticeably shorter than the 1024 "stream characters" YAML allows and that |
1292 | keys are noticeably shorter than the 1024 "stream characters" YAML allows |
1285 | you do not have characters with codepoint values outside the Unicode BMP |
1293 | and that you do not have characters with codepoint values outside the |
1286 | (basic multilingual page). YAML also does not allow C<\/> sequences in |
1294 | Unicode BMP (basic multilingual page). YAML also does not allow C<\/> |
1287 | strings (which JSON::XS does not I<currently> generate, but other JSON |
1295 | sequences in strings (which JSON::XS does not I<currently> generate, but |
1288 | generators might). |
1296 | other JSON generators might). |
1289 | |
1297 | |
1290 | There might be other incompatibilities that I am not aware of (or the YAML |
1298 | There might be other incompatibilities that I am not aware of (or the YAML |
1291 | specification has been changed yet again - it does so quite often). In |
1299 | specification has been changed yet again - it does so quite often). In |
1292 | general you should not try to generate YAML with a JSON generator or vice |
1300 | general you should not try to generate YAML with a JSON generator or vice |
1293 | versa, or try to parse JSON with a YAML parser or vice versa: chances are |
1301 | versa, or try to parse JSON with a YAML parser or vice versa: chances are |
… | |
… | |
1312 | that difficult or long) and finally make YAML compatible to it, and |
1320 | that difficult or long) and finally make YAML compatible to it, and |
1313 | educating users about the changes, instead of spreading lies about the |
1321 | educating users about the changes, instead of spreading lies about the |
1314 | real compatibility for many I<years> and trying to silence people who |
1322 | real compatibility for many I<years> and trying to silence people who |
1315 | point out that it isn't true. |
1323 | point out that it isn't true. |
1316 | |
1324 | |
|
|
1325 | Addendum/2009: the YAML 1.2 spec is still incompatible with JSON, even |
|
|
1326 | though the incompatibilities have been documented (and are known to Brian) |
|
|
1327 | for many years and the spec makes explicit claims that YAML is a superset |
|
|
1328 | of JSON. It would be so easy to fix, but apparently, bullying people and |
|
|
1329 | corrupting userdata is so much easier. |
|
|
1330 | |
1317 | =back |
1331 | =back |
1318 | |
1332 | |
1319 | |
1333 | |
1320 | =head2 SPEED |
1334 | =head2 SPEED |
1321 | |
1335 | |
… | |
… | |
1328 | a very short single-line JSON string (also available at |
1342 | a very short single-line JSON string (also available at |
1329 | L<http://dist.schmorp.de/misc/json/short.json>). |
1343 | L<http://dist.schmorp.de/misc/json/short.json>). |
1330 | |
1344 | |
1331 | {"method": "handleMessage", "params": ["user1", |
1345 | {"method": "handleMessage", "params": ["user1", |
1332 | "we were just talking"], "id": null, "array":[1,11,234,-5,1e5,1e7, |
1346 | "we were just talking"], "id": null, "array":[1,11,234,-5,1e5,1e7, |
1333 | true, false]} |
1347 | 1, 0]} |
1334 | |
1348 | |
1335 | It shows the number of encodes/decodes per second (JSON::XS uses |
1349 | It shows the number of encodes/decodes per second (JSON::XS uses |
1336 | the functional interface, while JSON::XS/2 uses the OO interface |
1350 | the functional interface, while JSON::XS/2 uses the OO interface |
1337 | with pretty-printing and hashkey sorting enabled, JSON::XS/3 enables |
1351 | with pretty-printing and hashkey sorting enabled, JSON::XS/3 enables |
1338 | shrink). Higher is better: |
1352 | shrink. JSON::DWIW/DS uses the deserialise function, while JSON::DWIW::FJ |
|
|
1353 | uses the from_json method). Higher is better: |
1339 | |
1354 | |
1340 | module | encode | decode | |
1355 | module | encode | decode | |
1341 | -----------|------------|------------| |
1356 | --------------|------------|------------| |
1342 | JSON 1.x | 4990.842 | 4088.813 | |
1357 | JSON::DWIW/DS | 86302.551 | 102300.098 | |
1343 | JSON::DWIW | 51653.990 | 71575.154 | |
1358 | JSON::DWIW/FJ | 86302.551 | 75983.768 | |
1344 | JSON::PC | 65948.176 | 74631.744 | |
1359 | JSON::PP | 15827.562 | 6638.658 | |
1345 | JSON::PP | 8931.652 | 3817.168 | |
1360 | JSON::Syck | 63358.066 | 47662.545 | |
1346 | JSON::Syck | 24877.248 | 27776.848 | |
1361 | JSON::XS | 511500.488 | 511500.488 | |
1347 | JSON::XS | 388361.481 | 227951.304 | |
1362 | JSON::XS/2 | 291271.111 | 388361.481 | |
1348 | JSON::XS/2 | 227951.304 | 218453.333 | |
1363 | JSON::XS/3 | 361577.931 | 361577.931 | |
1349 | JSON::XS/3 | 338250.323 | 218453.333 | |
1364 | Storable | 66788.280 | 265462.278 | |
1350 | Storable | 16500.016 | 135300.129 | |
|
|
1351 | -----------+------------+------------+ |
1365 | --------------+------------+------------+ |
1352 | |
1366 | |
1353 | That is, JSON::XS is about five times faster than JSON::DWIW on encoding, |
1367 | That is, JSON::XS is almost six times faster than JSON::DWIW on encoding, |
1354 | about three times faster on decoding, and over forty times faster |
1368 | about five times faster on decoding, and over thirty to seventy times |
1355 | than JSON, even with pretty-printing and key sorting. It also compares |
1369 | faster than JSON's pure perl implementation. It also compares favourably |
1356 | favourably to Storable for small amounts of data. |
1370 | to Storable for small amounts of data. |
1357 | |
1371 | |
1358 | Using a longer test string (roughly 18KB, generated from Yahoo! Locals |
1372 | Using a longer test string (roughly 18KB, generated from Yahoo! Locals |
1359 | search API (L<http://dist.schmorp.de/misc/json/long.json>). |
1373 | search API (L<http://dist.schmorp.de/misc/json/long.json>). |
1360 | |
1374 | |
1361 | module | encode | decode | |
1375 | module | encode | decode | |
1362 | -----------|------------|------------| |
1376 | --------------|------------|------------| |
1363 | JSON 1.x | 55.260 | 34.971 | |
1377 | JSON::DWIW/DS | 1647.927 | 2673.916 | |
1364 | JSON::DWIW | 825.228 | 1082.513 | |
1378 | JSON::DWIW/FJ | 1630.249 | 2596.128 | |
1365 | JSON::PC | 3571.444 | 2394.829 | |
|
|
1366 | JSON::PP | 210.987 | 32.574 | |
1379 | JSON::PP | 400.640 | 62.311 | |
1367 | JSON::Syck | 552.551 | 787.544 | |
1380 | JSON::Syck | 1481.040 | 1524.869 | |
1368 | JSON::XS | 5780.463 | 4854.519 | |
1381 | JSON::XS | 20661.596 | 9541.183 | |
1369 | JSON::XS/2 | 3869.998 | 4798.975 | |
1382 | JSON::XS/2 | 10683.403 | 9416.938 | |
1370 | JSON::XS/3 | 5862.880 | 4798.975 | |
1383 | JSON::XS/3 | 20661.596 | 9400.054 | |
1371 | Storable | 4445.002 | 5235.027 | |
1384 | Storable | 19765.806 | 10000.725 | |
1372 | -----------+------------+------------+ |
1385 | --------------+------------+------------+ |
1373 | |
1386 | |
1374 | Again, JSON::XS leads by far (except for Storable which non-surprisingly |
1387 | Again, JSON::XS leads by far (except for Storable which non-surprisingly |
1375 | decodes faster). |
1388 | decodes a bit faster). |
1376 | |
1389 | |
1377 | On large strings containing lots of high Unicode characters, some modules |
1390 | On large strings containing lots of high Unicode characters, some modules |
1378 | (such as JSON::PC) seem to decode faster than JSON::XS, but the result |
1391 | (such as JSON::PC) seem to decode faster than JSON::XS, but the result |
1379 | will be broken due to missing (or wrong) Unicode handling. Others refuse |
1392 | will be broken due to missing (or wrong) Unicode handling. Others refuse |
1380 | to decode or encode properly, so it was impossible to prepare a fair |
1393 | to decode or encode properly, so it was impossible to prepare a fair |
… | |
… | |
1416 | information you might want to make sure that exceptions thrown by JSON::XS |
1429 | information you might want to make sure that exceptions thrown by JSON::XS |
1417 | will not end up in front of untrusted eyes. |
1430 | will not end up in front of untrusted eyes. |
1418 | |
1431 | |
1419 | If you are using JSON::XS to return packets to consumption |
1432 | If you are using JSON::XS to return packets to consumption |
1420 | by JavaScript scripts in a browser you should have a look at |
1433 | by JavaScript scripts in a browser you should have a look at |
1421 | L<http://jpsykes.com/47/practical-csrf-and-json-security> to see whether |
1434 | L<http://blog.archive.jpsykes.com/47/practical-csrf-and-json-security/> to |
1422 | you are vulnerable to some common attack vectors (which really are browser |
1435 | see whether you are vulnerable to some common attack vectors (which really |
1423 | design bugs, but it is still you who will have to deal with it, as major |
1436 | are browser design bugs, but it is still you who will have to deal with |
1424 | browser developers care only for features, not about getting security |
1437 | it, as major browser developers care only for features, not about getting |
1425 | right). |
1438 | security right). |
1426 | |
1439 | |
1427 | |
1440 | |
1428 | =head1 THREADS |
1441 | =head1 THREADS |
1429 | |
1442 | |
1430 | This module is I<not> guaranteed to be thread safe and there are no |
1443 | This module is I<not> guaranteed to be thread safe and there are no |
1431 | plans to change this until Perl gets thread support (as opposed to the |
1444 | plans to change this until Perl gets thread support (as opposed to the |
1432 | horribly slow so-called "threads" which are simply slow and bloated |
1445 | horribly slow so-called "threads" which are simply slow and bloated |
1433 | process simulations - use fork, it's I<much> faster, cheaper, better). |
1446 | process simulations - use fork, it's I<much> faster, cheaper, better). |
1434 | |
1447 | |
1435 | (It might actually work, but you have been warned). |
1448 | (It might actually work, but you have been warned). |
|
|
1449 | |
|
|
1450 | |
|
|
1451 | =head1 THE PERILS OF SETLOCALE |
|
|
1452 | |
|
|
1453 | Sometimes people avoid the Perl locale support and directly call the |
|
|
1454 | system's setlocale function with C<LC_ALL>. |
|
|
1455 | |
|
|
1456 | This breaks both perl and modules such as JSON::XS, as stringification of |
|
|
1457 | numbers no longer works correctly (e.g. C<$x = 0.1; print "$x"+1> might |
|
|
1458 | print C<1>, and JSON::XS might output illegal JSON as JSON::XS relies on |
|
|
1459 | perl to stringify numbers). |
|
|
1460 | |
|
|
1461 | The solution is simple: don't call C<setlocale>, or use it for only those |
|
|
1462 | categories you need, such as C<LC_MESSAGES> or C<LC_CTYPE>. |
|
|
1463 | |
|
|
1464 | If you need C<LC_NUMERIC>, you should enable it only around the code that |
|
|
1465 | actually needs it (avoiding stringification of numbers), and restore it |
|
|
1466 | afterwards. |
1436 | |
1467 | |
1437 | |
1468 | |
1438 | =head1 BUGS |
1469 | =head1 BUGS |
1439 | |
1470 | |
1440 | While the goal of this module is to be correct, that unfortunately does |
1471 | While the goal of this module is to be correct, that unfortunately does |