ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/JSON-XS/README
(Generate patch)

Comparing JSON-XS/README (file contents):
Revision 1.22 by root, Wed Dec 5 10:59:27 2007 UTC vs.
Revision 1.37 by root, Thu May 23 09:32:02 2013 UTC

1NAME 1NAME
2 JSON::XS - JSON serialising/deserialising, done correctly and fast 2 JSON::XS - JSON serialising/deserialising, done correctly and fast
3 3
4 JSON::XS - 正しくて高速な JSON 4 JSON::XS - 正しくて高速な JSON シリアライザ/デシリアライザ
5 シリアライザ/デシリアライザ
6 (http://fleur.hio.jp/perldoc/mix/lib/JSON/XS.html) 5 (http://fleur.hio.jp/perldoc/mix/lib/JSON/XS.html)
7 6
8SYNOPSIS 7SYNOPSIS
9 use JSON::XS; 8 use JSON::XS;
10 9
… …
33 primary goal is to be *correct* and its secondary goal is to be *fast*. 32 primary goal is to be *correct* and its secondary goal is to be *fast*.
34 To reach the latter goal it was written in C. 33 To reach the latter goal it was written in C.
35 34
36 Beginning with version 2.0 of the JSON module, when both JSON and 35 Beginning with version 2.0 of the JSON module, when both JSON and
37 JSON::XS are installed, then JSON will fall back on JSON::XS (this can 36 JSON::XS are installed, then JSON will fall back on JSON::XS (this can
38 be overriden) with no overhead due to emulation (by inheritign 37 be overridden) with no overhead due to emulation (by inheriting
39 constructor and methods). If JSON::XS is not available, it will fall 38 constructor and methods). If JSON::XS is not available, it will fall
40 back to the compatible JSON::PP module as backend, so using JSON instead 39 back to the compatible JSON::PP module as backend, so using JSON instead
41 of JSON::XS gives you a portable JSON API that can be fast when you need 40 of JSON::XS gives you a portable JSON API that can be fast when you need
42 and doesn't require a C compiler when that is a problem. 41 and doesn't require a C compiler when that is a problem.
43 42
… …
45 to write yet another JSON module? While it seems there are many JSON 44 to write yet another JSON module? While it seems there are many JSON
46 modules, none of them correctly handle all corner cases, and in most 45 modules, none of them correctly handle all corner cases, and in most
47 cases their maintainers are unresponsive, gone missing, or not listening 46 cases their maintainers are unresponsive, gone missing, or not listening
48 to bug reports for other reasons. 47 to bug reports for other reasons.
49 48
50 See COMPARISON, below, for a comparison to some other JSON modules.
51
52 See MAPPING, below, on how JSON::XS maps perl values to JSON values and 49 See MAPPING, below, on how JSON::XS maps perl values to JSON values and
53 vice versa. 50 vice versa.
54 51
55 FEATURES 52 FEATURES
56 * correct Unicode handling 53 * correct Unicode handling
54
57 This module knows how to handle Unicode, and even documents how and 55 This module knows how to handle Unicode, documents how and when it
58 when it does so. 56 does so, and even documents what "correct" means.
59 57
60 * round-trip integrity 58 * round-trip integrity
59
61 When you serialise a perl data structure using only datatypes 60 When you serialise a perl data structure using only data types
62 supported by JSON, the deserialised data structure is identical on 61 supported by JSON and Perl, the deserialised data structure is
63 the Perl level. (e.g. the string "2.0" doesn't suddenly become "2" 62 identical on the Perl level. (e.g. the string "2.0" doesn't suddenly
64 just because it looks like a number). 63 become "2" just because it looks like a number). There *are* minor
64 exceptions to this, read the MAPPING section below to learn about
65 those.
65 66
66 * strict checking of JSON correctness 67 * strict checking of JSON correctness
68
67 There is no guessing, no generating of illegal JSON texts by 69 There is no guessing, no generating of illegal JSON texts by
68 default, and only JSON is accepted as input by default (the latter 70 default, and only JSON is accepted as input by default (the latter
69 is a security feature). 71 is a security feature).
70 72
71 * fast 73 * fast
72 Compared to other JSON modules, this module compares favourably in
73 terms of speed, too.
74 74
75 Compared to other JSON modules and other serialisers such as
76 Storable, this module usually compares favourably in terms of speed,
77 too.
78
75 * simple to use 79 * simple to use
80
76 This module has both a simple functional interface as well as an OO 81 This module has both a simple functional interface as well as an
77 interface. 82 object oriented interface interface.
78 83
79 * reasonably versatile output formats 84 * reasonably versatile output formats
85
80 You can choose between the most compact guaranteed single-line 86 You can choose between the most compact guaranteed-single-line
81 format possible (nice for simple line-based protocols), a pure-ascii 87 format possible (nice for simple line-based protocols), a pure-ASCII
82 format (for when your transport is not 8-bit clean, still supports 88 format (for when your transport is not 8-bit clean, still supports
83 the whole Unicode range), or a pretty-printed format (for when you 89 the whole Unicode range), or a pretty-printed format (for when you
84 want to read that stuff). Or you can combine those features in 90 want to read that stuff). Or you can combine those features in
85 whatever way you like. 91 whatever way you like.
86 92
… …
94 100
95 This function call is functionally identical to: 101 This function call is functionally identical to:
96 102
97 $json_text = JSON::XS->new->utf8->encode ($perl_scalar) 103 $json_text = JSON::XS->new->utf8->encode ($perl_scalar)
98 104
99 except being faster. 105 Except being faster.
100 106
101 $perl_scalar = decode_json $json_text 107 $perl_scalar = decode_json $json_text
102 The opposite of "encode_json": expects an UTF-8 (binary) string and 108 The opposite of "encode_json": expects an UTF-8 (binary) string and
103 tries to parse that as an UTF-8 encoded JSON text, returning the 109 tries to parse that as an UTF-8 encoded JSON text, returning the
104 resulting reference. Croaks on error. 110 resulting reference. Croaks on error.
105 111
106 This function call is functionally identical to: 112 This function call is functionally identical to:
107 113
108 $perl_scalar = JSON::XS->new->utf8->decode ($json_text) 114 $perl_scalar = JSON::XS->new->utf8->decode ($json_text)
109 115
110 except being faster. 116 Except being faster.
111 117
112 $is_boolean = JSON::XS::is_bool $scalar 118 $is_boolean = JSON::XS::is_bool $scalar
113 Returns true if the passed scalar represents either JSON::XS::true 119 Returns true if the passed scalar represents either JSON::XS::true
114 or JSON::XS::false, two constants that act like 1 and 0, 120 or JSON::XS::false, two constants that act like 1 and 0,
115 respectively and are used to represent JSON "true" and "false" 121 respectively and are used to represent JSON "true" and "false"
… …
125 1. Perl strings can store characters with ordinal values > 255. 131 1. Perl strings can store characters with ordinal values > 255.
126 This enables you to store Unicode characters as single characters in 132 This enables you to store Unicode characters as single characters in
127 a Perl string - very natural. 133 a Perl string - very natural.
128 134
129 2. Perl does *not* associate an encoding with your strings. 135 2. Perl does *not* associate an encoding with your strings.
130 Unless you force it to, e.g. when matching it against a regex, or 136 ... until you force it to, e.g. when matching it against a regex, or
131 printing the scalar to a file, in which case Perl either interprets 137 printing the scalar to a file, in which case Perl either interprets
132 your string as locale-encoded text, octets/binary, or as Unicode, 138 your string as locale-encoded text, octets/binary, or as Unicode,
133 depending on various settings. In no case is an encoding stored 139 depending on various settings. In no case is an encoding stored
134 together with your data, it is *use* that decides encoding, not any 140 together with your data, it is *use* that decides encoding, not any
135 magical metadata. 141 magical meta data.
136 142
137 3. The internal utf-8 flag has no meaning with regards to the encoding 143 3. The internal utf-8 flag has no meaning with regards to the encoding
138 of your string. 144 of your string.
139 Just ignore that flag unless you debug a Perl bug, a module written 145 Just ignore that flag unless you debug a Perl bug, a module written
140 in XS or want to dive into the internals of perl. Otherwise it will 146 in XS or want to dive into the internals of perl. Otherwise it will
… …
145 151
146 If you didn't know about that flag, just the better, pretend it 152 If you didn't know about that flag, just the better, pretend it
147 doesn't exist. 153 doesn't exist.
148 154
149 4. A "Unicode String" is simply a string where each character can be 155 4. A "Unicode String" is simply a string where each character can be
150 validly interpreted as a Unicode codepoint. 156 validly interpreted as a Unicode code point.
151 If you have UTF-8 encoded data, it is no longer a Unicode string, 157 If you have UTF-8 encoded data, it is no longer a Unicode string,
152 but a Unicode string encoded in UTF-8, giving you a binary string. 158 but a Unicode string encoded in UTF-8, giving you a binary string.
153 159
154 5. A string containing "high" (> 255) character values is *not* a UTF-8 160 5. A string containing "high" (> 255) character values is *not* a UTF-8
155 string. 161 string.
… …
185 191
186 If $enable is false, then the "encode" method will not escape 192 If $enable is false, then the "encode" method will not escape
187 Unicode characters unless required by the JSON syntax or other 193 Unicode characters unless required by the JSON syntax or other
188 flags. This results in a faster and more compact format. 194 flags. This results in a faster and more compact format.
189 195
196 See also the section *ENCODING/CODESET FLAG NOTES* later in this
197 document.
198
190 The main use for this flag is to produce JSON texts that can be 199 The main use for this flag is to produce JSON texts that can be
191 transmitted over a 7-bit channel, as the encoded JSON texts will not 200 transmitted over a 7-bit channel, as the encoded JSON texts will not
192 contain any 8 bit characters. 201 contain any 8 bit characters.
193 202
194 JSON::XS->new->ascii (1)->encode ([chr 0x10401]) 203 JSON::XS->new->ascii (1)->encode ([chr 0x10401])
… …
205 superset of latin1. 214 superset of latin1.
206 215
207 If $enable is false, then the "encode" method will not escape 216 If $enable is false, then the "encode" method will not escape
208 Unicode characters unless required by the JSON syntax or other 217 Unicode characters unless required by the JSON syntax or other
209 flags. 218 flags.
219
220 See also the section *ENCODING/CODESET FLAG NOTES* later in this
221 document.
210 222
211 The main use for this flag is efficiently encoding binary data as 223 The main use for this flag is efficiently encoding binary data as
212 JSON text, as most octets will not be escaped, resulting in a 224 JSON text, as most octets will not be escaped, resulting in a
213 smaller encoded size. The disadvantage is that the resulting JSON 225 smaller encoded size. The disadvantage is that the resulting JSON
214 text is encoded in latin1 (and must correctly be treated as such 226 text is encoded in latin1 (and must correctly be treated as such
… …
234 If $enable is false, then the "encode" method will return the JSON 246 If $enable is false, then the "encode" method will return the JSON
235 string as a (non-encoded) Unicode string, while "decode" expects 247 string as a (non-encoded) Unicode string, while "decode" expects
236 thus a Unicode string. Any decoding or encoding (e.g. to UTF-8 or 248 thus a Unicode string. Any decoding or encoding (e.g. to UTF-8 or
237 UTF-16) needs to be done yourself, e.g. using the Encode module. 249 UTF-16) needs to be done yourself, e.g. using the Encode module.
238 250
251 See also the section *ENCODING/CODESET FLAG NOTES* later in this
252 document.
253
239 Example, output UTF-16BE-encoded JSON: 254 Example, output UTF-16BE-encoded JSON:
240 255
241 use Encode; 256 use Encode;
242 $jsontext = encode "UTF-16BE", JSON::XS->new->encode ($object); 257 $jsontext = encode "UTF-16BE", JSON::XS->new->encode ($object);
243 258
… …
318 If $enable is false (the default), then "decode" will only accept 333 If $enable is false (the default), then "decode" will only accept
319 valid JSON texts. 334 valid JSON texts.
320 335
321 Currently accepted extensions are: 336 Currently accepted extensions are:
322 337
323 * list items can have an end-comma 338 * list items can have an end-comma
339
324 JSON *separates* array elements and key-value pairs with commas. 340 JSON *separates* array elements and key-value pairs with commas.
325 This can be annoying if you write JSON texts manually and want 341 This can be annoying if you write JSON texts manually and want
326 to be able to quickly append elements, so this extension accepts 342 to be able to quickly append elements, so this extension accepts
327 comma at the end of such items not just between them: 343 comma at the end of such items not just between them:
328 344
… …
333 { 349 {
334 "k1": "v1", 350 "k1": "v1",
335 "k2": "v2", <- this comma not normally allowed 351 "k2": "v2", <- this comma not normally allowed
336 } 352 }
337 353
338 * shell-style '#'-comments 354 * shell-style '#'-comments
355
339 Whenever JSON allows whitespace, shell-style comments are 356 Whenever JSON allows whitespace, shell-style comments are
340 additionally allowed. They are terminated by the first 357 additionally allowed. They are terminated by the first
341 carriage-return or line-feed character, after which more 358 carriage-return or line-feed character, after which more
342 white-space and comments are allowed. 359 white-space and comments are allowed.
343 360
… …
352 output JSON objects by sorting their keys. This is adding a 369 output JSON objects by sorting their keys. This is adding a
353 comparatively high overhead. 370 comparatively high overhead.
354 371
355 If $enable is false, then the "encode" method will output key-value 372 If $enable is false, then the "encode" method will output key-value
356 pairs in the order Perl stores them (which will likely change 373 pairs in the order Perl stores them (which will likely change
357 between runs of the same script). 374 between runs of the same script, and can change even within the same
375 run from 5.18 onwards).
358 376
359 This option is useful if you want the same data structure to be 377 This option is useful if you want the same data structure to be
360 encoded as the same JSON text (given the same overall settings). If 378 encoded as the same JSON text (given the same overall settings). If
361 it is disabled, the same hash might be encoded differently even if 379 it is disabled, the same hash might be encoded differently even if
362 contains the same data, as key-value pairs have no inherent ordering 380 contains the same data, as key-value pairs have no inherent ordering
363 in Perl. 381 in Perl.
364 382
365 This setting has no effect when decoding JSON texts. 383 This setting has no effect when decoding JSON texts.
384
385 This setting has currently no effect on tied hashes.
366 386
367 $json = $json->allow_nonref ([$enable]) 387 $json = $json->allow_nonref ([$enable])
368 $enabled = $json->get_allow_nonref 388 $enabled = $json->get_allow_nonref
369 If $enable is true (or missing), then the "encode" method can 389 If $enable is true (or missing), then the "encode" method can
370 convert a non-reference into its corresponding string, number or 390 convert a non-reference into its corresponding string, number or
… …
379 Example, encode a Perl scalar as JSON value with enabled 399 Example, encode a Perl scalar as JSON value with enabled
380 "allow_nonref", resulting in an invalid JSON text: 400 "allow_nonref", resulting in an invalid JSON text:
381 401
382 JSON::XS->new->allow_nonref->encode ("Hello, World!") 402 JSON::XS->new->allow_nonref->encode ("Hello, World!")
383 => "Hello, World!" 403 => "Hello, World!"
404
405 $json = $json->allow_unknown ([$enable])
406 $enabled = $json->get_allow_unknown
407 If $enable is true (or missing), then "encode" will *not* throw an
408 exception when it encounters values it cannot represent in JSON (for
409 example, filehandles) but instead will encode a JSON "null" value.
410 Note that blessed objects are not included here and are handled
411 separately by c<allow_nonref>.
412
413 If $enable is false (the default), then "encode" will throw an
414 exception when it encounters anything it cannot encode as JSON.
415
416 This option does not affect "decode" in any way, and it is
417 recommended to leave it off unless you know your communications
418 partner.
384 419
385 $json = $json->allow_blessed ([$enable]) 420 $json = $json->allow_blessed ([$enable])
386 $enabled = $json->get_allow_blessed 421 $enabled = $json->get_allow_blessed
387 If $enable is true (or missing), then the "encode" method will not 422 If $enable is true (or missing), then the "encode" method will not
388 barf when it encounters a blessed reference. Instead, the value of 423 barf when it encounters a blessed reference. Instead, the value of
… …
523 saving space. 558 saving space.
524 559
525 $json = $json->max_depth ([$maximum_nesting_depth]) 560 $json = $json->max_depth ([$maximum_nesting_depth])
526 $max_depth = $json->get_max_depth 561 $max_depth = $json->get_max_depth
527 Sets the maximum nesting level (default 512) accepted while encoding 562 Sets the maximum nesting level (default 512) accepted while encoding
528 or decoding. If the JSON text or Perl data structure has an equal or 563 or decoding. If a higher nesting level is detected in JSON text or a
529 higher nesting level then this limit, then the encoder and decoder 564 Perl data structure, then the encoder and decoder will stop and
530 will stop and croak at that point. 565 croak at that point.
531 566
532 Nesting level is defined by number of hash- or arrayrefs that the 567 Nesting level is defined by number of hash- or arrayrefs that the
533 encoder needs to traverse to reach a given point or the number of 568 encoder needs to traverse to reach a given point or the number of
534 "{" or "[" characters without their matching closing parenthesis 569 "{" or "[" characters without their matching closing parenthesis
535 crossed to reach a given character in a string. 570 crossed to reach a given character in a string.
536 571
537 Setting the maximum depth to one disallows any nesting, so that 572 Setting the maximum depth to one disallows any nesting, so that
538 ensures that the object is only a single hash/object or array. 573 ensures that the object is only a single hash/object or array.
539 574
540 The argument to "max_depth" will be rounded up to the next highest
541 power of two. If no argument is given, the highest possible setting 575 If no argument is given, the highest possible setting will be used,
542 will be used, which is rarely useful. 576 which is rarely useful.
577
578 Note that nesting is implemented by recursion in C. The default
579 value has been chosen to be as large as typical operating systems
580 allow without crashing.
543 581
544 See SECURITY CONSIDERATIONS, below, for more info on why this is 582 See SECURITY CONSIDERATIONS, below, for more info on why this is
545 useful. 583 useful.
546 584
547 $json = $json->max_size ([$maximum_string_size]) 585 $json = $json->max_size ([$maximum_string_size])
548 $max_size = $json->get_max_size 586 $max_size = $json->get_max_size
549 Set the maximum length a JSON text may have (in bytes) where 587 Set the maximum length a JSON text may have (in bytes) where
550 decoding is being attempted. The default is 0, meaning no limit. 588 decoding is being attempted. The default is 0, meaning no limit.
551 When "decode" is called on a string longer then this number of 589 When "decode" is called on a string that is longer then this many
552 characters it will not attempt to decode the string but throw an 590 bytes, it will not attempt to decode the string but throw an
553 exception. This setting has no effect on "encode" (yet). 591 exception. This setting has no effect on "encode" (yet).
554 592
555 The argument to "max_size" will be rounded up to the next highest
556 power of two (so may be more than requested). If no argument is
557 given, the limit check will be deactivated (same as when 0 is 593 If no argument is given, the limit check will be deactivated (same
558 specified). 594 as when 0 is specified).
559 595
560 See SECURITY CONSIDERATIONS, below, for more info on why this is 596 See SECURITY CONSIDERATIONS, below, for more info on why this is
561 useful. 597 useful.
562 598
563 $json_text = $json->encode ($perl_scalar) 599 $json_text = $json->encode ($perl_scalar)
… …
588 and you need to know where the JSON text ends. 624 and you need to know where the JSON text ends.
589 625
590 JSON::XS->new->decode_prefix ("[1] the tail") 626 JSON::XS->new->decode_prefix ("[1] the tail")
591 => ([], 3) 627 => ([], 3)
592 628
629INCREMENTAL PARSING
630 In some cases, there is the need for incremental parsing of JSON texts.
631 While this module always has to keep both JSON text and resulting Perl
632 data structure in memory at one time, it does allow you to parse a JSON
633 stream incrementally. It does so by accumulating text until it has a
634 full JSON object, which it then can decode. This process is similar to
635 using "decode_prefix" to see if a full JSON object is available, but is
636 much more efficient (and can be implemented with a minimum of method
637 calls).
638
639 JSON::XS will only attempt to parse the JSON text once it is sure it has
640 enough text to get a decisive result, using a very simple but truly
641 incremental parser. This means that it sometimes won't stop as early as
642 the full parser, for example, it doesn't detect mismatched parentheses.
643 The only thing it guarantees is that it starts decoding as soon as a
644 syntactically valid JSON text has been seen. This means you need to set
645 resource limits (e.g. "max_size") to ensure the parser will stop parsing
646 in the presence if syntax errors.
647
648 The following methods implement this incremental parser.
649
650 [void, scalar or list context] = $json->incr_parse ([$string])
651 This is the central parsing function. It can both append new text
652 and extract objects from the stream accumulated so far (both of
653 these functions are optional).
654
655 If $string is given, then this string is appended to the already
656 existing JSON fragment stored in the $json object.
657
658 After that, if the function is called in void context, it will
659 simply return without doing anything further. This can be used to
660 add more text in as many chunks as you want.
661
662 If the method is called in scalar context, then it will try to
663 extract exactly *one* JSON object. If that is successful, it will
664 return this object, otherwise it will return "undef". If there is a
665 parse error, this method will croak just as "decode" would do (one
666 can then use "incr_skip" to skip the errornous part). This is the
667 most common way of using the method.
668
669 And finally, in list context, it will try to extract as many objects
670 from the stream as it can find and return them, or the empty list
671 otherwise. For this to work, there must be no separators between the
672 JSON objects or arrays, instead they must be concatenated
673 back-to-back. If an error occurs, an exception will be raised as in
674 the scalar context case. Note that in this case, any
675 previously-parsed JSON texts will be lost.
676
677 Example: Parse some JSON arrays/objects in a given string and return
678 them.
679
680 my @objs = JSON::XS->new->incr_parse ("[5][7][1,2]");
681
682 $lvalue_string = $json->incr_text
683 This method returns the currently stored JSON fragment as an lvalue,
684 that is, you can manipulate it. This *only* works when a preceding
685 call to "incr_parse" in *scalar context* successfully returned an
686 object. Under all other circumstances you must not call this
687 function (I mean it. although in simple tests it might actually
688 work, it *will* fail under real world conditions). As a special
689 exception, you can also call this method before having parsed
690 anything.
691
692 This function is useful in two cases: a) finding the trailing text
693 after a JSON object or b) parsing multiple JSON objects separated by
694 non-JSON text (such as commas).
695
696 $json->incr_skip
697 This will reset the state of the incremental parser and will remove
698 the parsed text from the input buffer so far. This is useful after
699 "incr_parse" died, in which case the input buffer and incremental
700 parser state is left unchanged, to skip the text parsed so far and
701 to reset the parse state.
702
703 The difference to "incr_reset" is that only text until the parse
704 error occured is removed.
705
706 $json->incr_reset
707 This completely resets the incremental parser, that is, after this
708 call, it will be as if the parser had never parsed anything.
709
710 This is useful if you want to repeatedly parse JSON objects and want
711 to ignore any trailing data, which means you have to reset the
712 parser after each successful decode.
713
714 LIMITATIONS
715 All options that affect decoding are supported, except "allow_nonref".
716 The reason for this is that it cannot be made to work sensibly: JSON
717 objects and arrays are self-delimited, i.e. you can concatenate them
718 back to back and still decode them perfectly. This does not hold true
719 for JSON numbers, however.
720
721 For example, is the string 1 a single JSON number, or is it simply the
722 start of 12? Or is 12 a single JSON number, or the concatenation of 1
723 and 2? In neither case you can tell, and this is why JSON::XS takes the
724 conservative route and disallows this case.
725
726 EXAMPLES
727 Some examples will make all this clearer. First, a simple example that
728 works similarly to "decode_prefix": We want to decode the JSON object at
729 the start of a string and identify the portion after the JSON object:
730
731 my $text = "[1,2,3] hello";
732
733 my $json = new JSON::XS;
734
735 my $obj = $json->incr_parse ($text)
736 or die "expected JSON object or array at beginning of string";
737
738 my $tail = $json->incr_text;
739 # $tail now contains " hello"
740
741 Easy, isn't it?
742
743 Now for a more complicated example: Imagine a hypothetical protocol
744 where you read some requests from a TCP stream, and each request is a
745 JSON array, without any separation between them (in fact, it is often
746 useful to use newlines as "separators", as these get interpreted as
747 whitespace at the start of the JSON text, which makes it possible to
748 test said protocol with "telnet"...).
749
750 Here is how you'd do it (it is trivial to write this in an event-based
751 manner):
752
753 my $json = new JSON::XS;
754
755 # read some data from the socket
756 while (sysread $socket, my $buf, 4096) {
757
758 # split and decode as many requests as possible
759 for my $request ($json->incr_parse ($buf)) {
760 # act on the $request
761 }
762 }
763
764 Another complicated example: Assume you have a string with JSON objects
765 or arrays, all separated by (optional) comma characters (e.g. "[1],[2],
766 [3]"). To parse them, we have to skip the commas between the JSON texts,
767 and here is where the lvalue-ness of "incr_text" comes in useful:
768
769 my $text = "[1],[2], [3]";
770 my $json = new JSON::XS;
771
772 # void context, so no parsing done
773 $json->incr_parse ($text);
774
775 # now extract as many objects as possible. note the
776 # use of scalar context so incr_text can be called.
777 while (my $obj = $json->incr_parse) {
778 # do something with $obj
779
780 # now skip the optional comma
781 $json->incr_text =~ s/^ \s* , //x;
782 }
783
784 Now lets go for a very complex example: Assume that you have a gigantic
785 JSON array-of-objects, many gigabytes in size, and you want to parse it,
786 but you cannot load it into memory fully (this has actually happened in
787 the real world :).
788
789 Well, you lost, you have to implement your own JSON parser. But JSON::XS
790 can still help you: You implement a (very simple) array parser and let
791 JSON decode the array elements, which are all full JSON objects on their
792 own (this wouldn't work if the array elements could be JSON numbers, for
793 example):
794
795 my $json = new JSON::XS;
796
797 # open the monster
798 open my $fh, "<bigfile.json"
799 or die "bigfile: $!";
800
801 # first parse the initial "["
802 for (;;) {
803 sysread $fh, my $buf, 65536
804 or die "read error: $!";
805 $json->incr_parse ($buf); # void context, so no parsing
806
807 # Exit the loop once we found and removed(!) the initial "[".
808 # In essence, we are (ab-)using the $json object as a simple scalar
809 # we append data to.
810 last if $json->incr_text =~ s/^ \s* \[ //x;
811 }
812
813 # now we have the skipped the initial "[", so continue
814 # parsing all the elements.
815 for (;;) {
816 # in this loop we read data until we got a single JSON object
817 for (;;) {
818 if (my $obj = $json->incr_parse) {
819 # do something with $obj
820 last;
821 }
822
823 # add more data
824 sysread $fh, my $buf, 65536
825 or die "read error: $!";
826 $json->incr_parse ($buf); # void context, so no parsing
827 }
828
829 # in this loop we read data until we either found and parsed the
830 # separating "," between elements, or the final "]"
831 for (;;) {
832 # first skip whitespace
833 $json->incr_text =~ s/^\s*//;
834
835 # if we find "]", we are done
836 if ($json->incr_text =~ s/^\]//) {
837 print "finished.\n";
838 exit;
839 }
840
841 # if we find ",", we can continue with the next element
842 if ($json->incr_text =~ s/^,//) {
843 last;
844 }
845
846 # if we find anything else, we have a parse error!
847 if (length $json->incr_text) {
848 die "parse error near ", $json->incr_text;
849 }
850
851 # else add more data
852 sysread $fh, my $buf, 65536
853 or die "read error: $!";
854 $json->incr_parse ($buf); # void context, so no parsing
855 }
856
857 This is a complex example, but most of the complexity comes from the
858 fact that we are trying to be correct (bear with me if I am wrong, I
859 never ran the above example :).
860
593MAPPING 861MAPPING
594 This section describes how JSON::XS maps Perl values to JSON values and 862 This section describes how JSON::XS maps Perl values to JSON values and
595 vice versa. These mappings are designed to "do the right thing" in most 863 vice versa. These mappings are designed to "do the right thing" in most
596 circumstances automatically, preserving round-tripping characteristics 864 circumstances automatically, preserving round-tripping characteristics
597 (what you put in comes out as something equivalent). 865 (what you put in comes out as something equivalent).
… …
618 A JSON number becomes either an integer, numeric (floating point) or 886 A JSON number becomes either an integer, numeric (floating point) or
619 string scalar in perl, depending on its range and any fractional 887 string scalar in perl, depending on its range and any fractional
620 parts. On the Perl level, there is no difference between those as 888 parts. On the Perl level, there is no difference between those as
621 Perl handles all the conversion details, but an integer may take 889 Perl handles all the conversion details, but an integer may take
622 slightly less memory and might represent more values exactly than 890 slightly less memory and might represent more values exactly than
623 (floating point) numbers. 891 floating point numbers.
624 892
625 If the number consists of digits only, JSON::XS will try to 893 If the number consists of digits only, JSON::XS will try to
626 represent it as an integer value. If that fails, it will try to 894 represent it as an integer value. If that fails, it will try to
627 represent it as a numeric (floating point) value if that is possible 895 represent it as a numeric (floating point) value if that is possible
628 without loss of precision. Otherwise it will preserve the number as 896 without loss of precision. Otherwise it will preserve the number as
629 a string value. 897 a string value (in which case you lose roundtripping ability, as the
898 JSON number will be re-encoded toa JSON string).
630 899
631 Numbers containing a fractional or exponential part will always be 900 Numbers containing a fractional or exponential part will always be
632 represented as numeric (floating point) values, possibly at a loss 901 represented as numeric (floating point) values, possibly at a loss
633 of precision. 902 of precision (in which case you might lose perfect roundtripping
903 ability, but the JSON number will still be re-encoded as a JSON
904 number).
634 905
635 This might create round-tripping problems as numbers might become 906 Note that precision is not accuracy - binary floating point values
636 strings, but as Perl is typeless there is no other way to do it. 907 cannot represent most decimal fractions exactly, and when converting
908 from and to floating point, JSON::XS only guarantees precision up to
909 but not including the leats significant bit.
637 910
638 true, false 911 true, false
639 These JSON atoms become "JSON::XS::true" and "JSON::XS::false", 912 These JSON atoms become "JSON::XS::true" and "JSON::XS::false",
640 respectively. They are overloaded to act almost exactly like the 913 respectively. They are overloaded to act almost exactly like the
641 numbers 1 and 0. You can check whether a scalar is a JSON boolean by 914 numbers 1 and 0. You can check whether a scalar is a JSON boolean by
… …
669 an exception to be thrown, except for references to the integers 0 942 an exception to be thrown, except for references to the integers 0
670 and 1, which get turned into "false" and "true" atoms in JSON. You 943 and 1, which get turned into "false" and "true" atoms in JSON. You
671 can also use "JSON::XS::false" and "JSON::XS::true" to improve 944 can also use "JSON::XS::false" and "JSON::XS::true" to improve
672 readability. 945 readability.
673 946
674 encode_json [\0,JSON::XS::true] # yields [false,true] 947 encode_json [\0, JSON::XS::true] # yields [false,true]
675 948
676 JSON::XS::true, JSON::XS::false 949 JSON::XS::true, JSON::XS::false
677 These special values become JSON true and JSON false values, 950 These special values become JSON true and JSON false values,
678 respectively. You can also use "\1" and "\0" directly if you want. 951 respectively. You can also use "\1" and "\0" directly if you want.
679 952
680 blessed objects 953 blessed objects
681 Blessed objects are not allowed. JSON::XS currently tries to encode 954 Blessed objects are not directly representable in JSON. See the
682 their underlying representation (hash- or arrayref), but this 955 "allow_blessed" and "convert_blessed" methods on various options on
683 behaviour might change in future versions. 956 how to deal with this: basically, you can choose between throwing an
957 exception, encoding the reference as if it weren't blessed, or
958 provide your own serialiser method.
684 959
685 simple scalars 960 simple scalars
686 Simple Perl scalars (any scalar that is not a reference) are the 961 Simple Perl scalars (any scalar that is not a reference) are the
687 most difficult objects to encode: JSON::XS will encode undefined 962 most difficult objects to encode: JSON::XS will encode undefined
688 scalars as JSON null value, scalars that have last been used in a 963 scalars as JSON "null" values, scalars that have last been used in a
689 string context before encoding as JSON strings and anything else as 964 string context before encoding as JSON strings, and anything else as
690 number value: 965 number value:
691 966
692 # dump as number 967 # dump as number
693 encode_json [2] # yields [2] 968 encode_json [2] # yields [2]
694 encode_json [-3.0e17] # yields [-3e+17] 969 encode_json [-3.0e17] # yields [-3e+17]
… …
713 my $x = "3"; # some variable containing a string 988 my $x = "3"; # some variable containing a string
714 $x += 0; # numify it, ensuring it will be dumped as a number 989 $x += 0; # numify it, ensuring it will be dumped as a number
715 $x *= 1; # same thing, the choice is yours. 990 $x *= 1; # same thing, the choice is yours.
716 991
717 You can not currently force the type in other, less obscure, ways. 992 You can not currently force the type in other, less obscure, ways.
718 Tell me if you need this capability. 993 Tell me if you need this capability (but don't forget to explain why
994 it's needed :).
719 995
720COMPARISON 996 Note that numerical precision has the same meaning as under Perl (so
721 As already mentioned, this module was created because none of the 997 binary to decimal conversion follows the same rules as in Perl,
722 existing JSON modules could be made to work correctly. First I will 998 which can differ to other languages). Also, your perl interpreter
723 describe the problems (or pleasures) I encountered with various existing 999 might expose extensions to the floating point numbers of your
724 JSON modules, followed by some benchmark values. JSON::XS was designed 1000 platform, such as infinities or NaN's - these cannot be represented
725 not to suffer from any of these problems or limitations. 1001 in JSON, and it is an error to pass those in.
726 1002
727 JSON 1.07 1003ENCODING/CODESET FLAG NOTES
728 Slow (but very portable, as it is written in pure Perl). 1004 The interested reader might have seen a number of flags that signify
1005 encodings or codesets - "utf8", "latin1" and "ascii". There seems to be
1006 some confusion on what these do, so here is a short comparison:
729 1007
730 Undocumented/buggy Unicode handling (how JSON handles Unicode values 1008 "utf8" controls whether the JSON text created by "encode" (and expected
731 is undocumented. One can get far by feeding it Unicode strings and 1009 by "decode") is UTF-8 encoded or not, while "latin1" and "ascii" only
732 doing en-/decoding oneself, but Unicode escapes are not working 1010 control whether "encode" escapes character values outside their
1011 respective codeset range. Neither of these flags conflict with each
1012 other, although some combinations make less sense than others.
1013
1014 Care has been taken to make all flags symmetrical with respect to
1015 "encode" and "decode", that is, texts encoded with any combination of
1016 these flag values will be correctly decoded when the same flags are used
1017 - in general, if you use different flag settings while encoding vs. when
1018 decoding you likely have a bug somewhere.
1019
1020 Below comes a verbose discussion of these flags. Note that a "codeset"
1021 is simply an abstract set of character-codepoint pairs, while an
1022 encoding takes those codepoint numbers and *encodes* them, in our case
1023 into octets. Unicode is (among other things) a codeset, UTF-8 is an
1024 encoding, and ISO-8859-1 (= latin 1) and ASCII are both codesets *and*
1025 encodings at the same time, which can be confusing.
1026
1027 "utf8" flag disabled
1028 When "utf8" is disabled (the default), then "encode"/"decode"
1029 generate and expect Unicode strings, that is, characters with high
1030 ordinal Unicode values (> 255) will be encoded as such characters,
1031 and likewise such characters are decoded as-is, no canges to them
1032 will be done, except "(re-)interpreting" them as Unicode codepoints
1033 or Unicode characters, respectively (to Perl, these are the same
1034 thing in strings unless you do funny/weird/dumb stuff).
1035
1036 This is useful when you want to do the encoding yourself (e.g. when
1037 you want to have UTF-16 encoded JSON texts) or when some other layer
1038 does the encoding for you (for example, when printing to a terminal
1039 using a filehandle that transparently encodes to UTF-8 you certainly
1040 do NOT want to UTF-8 encode your data first and have Perl encode it
1041 another time).
1042
1043 "utf8" flag enabled
1044 If the "utf8"-flag is enabled, "encode"/"decode" will encode all
1045 characters using the corresponding UTF-8 multi-byte sequence, and
1046 will expect your input strings to be encoded as UTF-8, that is, no
1047 "character" of the input string must have any value > 255, as UTF-8
1048 does not allow that.
1049
1050 The "utf8" flag therefore switches between two modes: disabled means
1051 you will get a Unicode string in Perl, enabled means you get an
1052 UTF-8 encoded octet/binary string in Perl.
1053
1054 "latin1" or "ascii" flags enabled
1055 With "latin1" (or "ascii") enabled, "encode" will escape characters
1056 with ordinal values > 255 (> 127 with "ascii") and encode the
1057 remaining characters as specified by the "utf8" flag.
1058
1059 If "utf8" is disabled, then the result is also correctly encoded in
1060 those character sets (as both are proper subsets of Unicode, meaning
1061 that a Unicode string with all character values < 256 is the same
1062 thing as a ISO-8859-1 string, and a Unicode string with all
1063 character values < 128 is the same thing as an ASCII string in
733 properly). 1064 Perl).
734 1065
735 No round-tripping (strings get clobbered if they look like numbers, 1066 If "utf8" is enabled, you still get a correct UTF-8-encoded string,
736 e.g. the string 2.0 will encode to 2.0 instead of "2.0", and that 1067 regardless of these flags, just some more characters will be escaped
737 will decode into the number 2. 1068 using "\uXXXX" then before.
738 1069
739 JSON::PC 0.01 1070 Note that ISO-8859-1-*encoded* strings are not compatible with UTF-8
740 Very fast. 1071 encoding, while ASCII-encoded strings are. That is because the
1072 ISO-8859-1 encoding is NOT a subset of UTF-8 (despite the ISO-8859-1
1073 *codeset* being a subset of Unicode), while ASCII is.
741 1074
742 Undocumented/buggy Unicode handling. 1075 Surprisingly, "decode" will ignore these flags and so treat all
1076 input values as governed by the "utf8" flag. If it is disabled, this
1077 allows you to decode ISO-8859-1- and ASCII-encoded strings, as both
1078 strict subsets of Unicode. If it is enabled, you can correctly
1079 decode UTF-8 encoded strings.
743 1080
744 No round-tripping. 1081 So neither "latin1" nor "ascii" are incompatible with the "utf8"
1082 flag - they only govern when the JSON output engine escapes a
1083 character or not.
745 1084
746 Has problems handling many Perl values (e.g. regex results and other 1085 The main use for "latin1" is to relatively efficiently store binary
747 magic values will make it croak). 1086 data as JSON, at the expense of breaking compatibility with most
1087 JSON decoders.
748 1088
749 Does not even generate valid JSON ("{1,2}" gets converted to "{1:2}" 1089 The main use for "ascii" is to force the output to not contain
750 which is not a valid JSON text. 1090 characters with values > 127, which means you can interpret the
1091 resulting string as UTF-8, ISO-8859-1, ASCII, KOI8-R or most about
1092 any character set and 8-bit-encoding, and still get the same data
1093 structure back. This is useful when your channel for JSON transfer
1094 is not 8-bit clean or the encoding might be mangled in between (e.g.
1095 in mail), and works because ASCII is a proper subset of most 8-bit
1096 and multibyte encodings in use in the world.
751 1097
752 Unmaintained (maintainer unresponsive for many months, bugs are not 1098 JSON and ECMAscript
753 getting fixed). 1099 JSON syntax is based on how literals are represented in javascript (the
1100 not-standardised predecessor of ECMAscript) which is presumably why it
1101 is called "JavaScript Object Notation".
754 1102
755 JSON::Syck 0.21 1103 However, JSON is not a subset (and also not a superset of course) of
756 Very buggy (often crashes). 1104 ECMAscript (the standard) or javascript (whatever browsers actually
1105 implement).
757 1106
758 Very inflexible (no human-readable format supported, format pretty 1107 If you want to use javascript's "eval" function to "parse" JSON, you
759 much undocumented. I need at least a format for easy reading by 1108 might run into parse errors for valid JSON texts, or the resulting data
760 humans and a single-line compact format for use in a protocol, and 1109 structure might not be queryable:
761 preferably a way to generate ASCII-only JSON texts).
762 1110
763 Completely broken (and confusingly documented) Unicode handling 1111 One of the problems is that U+2028 and U+2029 are valid characters
764 (Unicode escapes are not working properly, you need to set 1112 inside JSON strings, but are not allowed in ECMAscript string literals,
765 ImplicitUnicode to *different* values on en- and decoding to get 1113 so the following Perl fragment will not output something that can be
766 symmetric behaviour). 1114 guaranteed to be parsable by javascript's "eval":
767 1115
768 No round-tripping (simple cases work, but this depends on whether 1116 use JSON::XS;
769 the scalar value was used in a numeric context or not).
770 1117
771 Dumping hashes may skip hash values depending on iterator state. 1118 print encode_json [chr 0x2028];
772 1119
773 Unmaintained (maintainer unresponsive for many months, bugs are not 1120 The right fix for this is to use a proper JSON parser in your javascript
774 getting fixed). 1121 programs, and not rely on "eval" (see for example Douglas Crockford's
1122 json2.js parser).
775 1123
776 Does not check input for validity (i.e. will accept non-JSON input 1124 If this is not an option, you can, as a stop-gap measure, simply encode
777 and return "something" instead of raising an exception. This is a 1125 to ASCII-only JSON:
778 security issue: imagine two banks transferring money between each
779 other using JSON. One bank might parse a given non-JSON request and
780 deduct money, while the other might reject the transaction with a
781 syntax error. While a good protocol will at least recover, that is
782 extra unnecessary work and the transaction will still not succeed).
783 1126
784 JSON::DWIW 0.04 1127 use JSON::XS;
785 Very fast. Very natural. Very nice.
786 1128
787 Undocumented Unicode handling (but the best of the pack. Unicode 1129 print JSON::XS->new->ascii->encode ([chr 0x2028]);
788 escapes still don't get parsed properly).
789 1130
790 Very inflexible. 1131 Note that this will enlarge the resulting JSON text quite a bit if you
1132 have many non-ASCII characters. You might be tempted to run some regexes
1133 to only escape U+2028 and U+2029, e.g.:
791 1134
792 No round-tripping. 1135 # DO NOT USE THIS!
1136 my $json = JSON::XS->new->utf8->encode ([chr 0x2028]);
1137 $json =~ s/\xe2\x80\xa8/\\u2028/g; # escape U+2028
1138 $json =~ s/\xe2\x80\xa9/\\u2029/g; # escape U+2029
1139 print $json;
793 1140
794 Does not generate valid JSON texts (key strings are often unquoted, 1141 Note that *this is a bad idea*: the above only works for U+2028 and
795 empty keys result in nothing being output) 1142 U+2029 and thus only for fully ECMAscript-compliant parsers. Many
1143 existing javascript implementations, however, have issues with other
1144 characters as well - using "eval" naively simply *will* cause problems.
796 1145
797 Does not check input for validity. 1146 Another problem is that some javascript implementations reserve some
1147 property names for their own purposes (which probably makes them
1148 non-ECMAscript-compliant). For example, Iceweasel reserves the
1149 "__proto__" property name for its own purposes.
1150
1151 If that is a problem, you could parse try to filter the resulting JSON
1152 output for these property strings, e.g.:
1153
1154 $json =~ s/"__proto__"\s*:/"__proto__renamed":/g;
1155
1156 This works because "__proto__" is not valid outside of strings, so every
1157 occurence of ""__proto__"\s*:" must be a string used as property name.
1158
1159 If you know of other incompatibilities, please let me know.
798 1160
799 JSON and YAML 1161 JSON and YAML
800 You often hear that JSON is a subset (or a close subset) of YAML. This 1162 You often hear that JSON is a subset of YAML. This is, however, a mass
801 is, however, a mass hysteria and very far from the truth. In general, 1163 hysteria(*) and very far from the truth (as of the time of this
802 there is no way to configure JSON::XS to output a data structure as 1164 writing), so let me state it clearly: *in general, there is no way to
803 valid YAML. 1165 configure JSON::XS to output a data structure as valid YAML* that works
1166 in all cases.
804 1167
805 If you really must use JSON::XS to generate YAML, you should use this 1168 If you really must use JSON::XS to generate YAML, you should use this
806 algorithm (subject to change in future versions): 1169 algorithm (subject to change in future versions):
807 1170
808 my $to_yaml = JSON::XS->new->utf8->space_after (1); 1171 my $to_yaml = JSON::XS->new->utf8->space_after (1);
809 my $yaml = $to_yaml->encode ($ref) . "\n"; 1172 my $yaml = $to_yaml->encode ($ref) . "\n";
810 1173
811 This will usually generate JSON texts that also parse as valid YAML. 1174 This will *usually* generate JSON texts that also parse as valid YAML.
812 Please note that YAML has hardcoded limits on (simple) object key 1175 Please note that YAML has hardcoded limits on (simple) object key
813 lengths that JSON doesn't have, so you should make sure that your hash 1176 lengths that JSON doesn't have and also has different and incompatible
1177 unicode character escape syntax, so you should make sure that your hash
814 keys are noticeably shorter than the 1024 characters YAML allows. 1178 keys are noticeably shorter than the 1024 "stream characters" YAML
1179 allows and that you do not have characters with codepoint values outside
1180 the Unicode BMP (basic multilingual page). YAML also does not allow "\/"
1181 sequences in strings (which JSON::XS does not *currently* generate, but
1182 other JSON generators might).
815 1183
816 There might be other incompatibilities that I am not aware of. In 1184 There might be other incompatibilities that I am not aware of (or the
1185 YAML specification has been changed yet again - it does so quite often).
817 general you should not try to generate YAML with a JSON generator or 1186 In general you should not try to generate YAML with a JSON generator or
818 vice versa, or try to parse JSON with a YAML parser or vice versa: 1187 vice versa, or try to parse JSON with a YAML parser or vice versa:
819 chances are high that you will run into severe interoperability 1188 chances are high that you will run into severe interoperability problems
820 problems. 1189 when you least expect it.
1190
1191 (*) I have been pressured multiple times by Brian Ingerson (one of the
1192 authors of the YAML specification) to remove this paragraph, despite
1193 him acknowledging that the actual incompatibilities exist. As I was
1194 personally bitten by this "JSON is YAML" lie, I refused and said I
1195 will continue to educate people about these issues, so others do not
1196 run into the same problem again and again. After this, Brian called
1197 me a (quote)*complete and worthless idiot*(unquote).
1198
1199 In my opinion, instead of pressuring and insulting people who
1200 actually clarify issues with YAML and the wrong statements of some
1201 of its proponents, I would kindly suggest reading the JSON spec
1202 (which is not that difficult or long) and finally make YAML
1203 compatible to it, and educating users about the changes, instead of
1204 spreading lies about the real compatibility for many *years* and
1205 trying to silence people who point out that it isn't true.
1206
1207 Addendum/2009: the YAML 1.2 spec is still incompatible with JSON,
1208 even though the incompatibilities have been documented (and are
1209 known to Brian) for many years and the spec makes explicit claims
1210 that YAML is a superset of JSON. It would be so easy to fix, but
1211 apparently, bullying people and corrupting userdata is so much
1212 easier.
821 1213
822 SPEED 1214 SPEED
823 It seems that JSON::XS is surprisingly fast, as shown in the following 1215 It seems that JSON::XS is surprisingly fast, as shown in the following
824 tables. They have been generated with the help of the "eg/bench" program 1216 tables. They have been generated with the help of the "eg/bench" program
825 in the JSON::XS distribution, to make it easy to compare on your own 1217 in the JSON::XS distribution, to make it easy to compare on your own
826 system. 1218 system.
827 1219
828 First comes a comparison between various modules using a very short 1220 First comes a comparison between various modules using a very short
829 single-line JSON string: 1221 single-line JSON string (also available at
1222 <http://dist.schmorp.de/misc/json/short.json>).
830 1223
831 {"method": "handleMessage", "params": ["user1", "we were just talking"], \ 1224 {"method": "handleMessage", "params": ["user1",
832 "id": null, "array":[1,11,234,-5,1e5,1e7, true, false]} 1225 "we were just talking"], "id": null, "array":[1,11,234,-5,1e5,1e7,
1226 1, 0]}
833 1227
834 It shows the number of encodes/decodes per second (JSON::XS uses the 1228 It shows the number of encodes/decodes per second (JSON::XS uses the
835 functional interface, while JSON::XS/2 uses the OO interface with 1229 functional interface, while JSON::XS/2 uses the OO interface with
836 pretty-printing and hashkey sorting enabled, JSON::XS/3 enables shrink). 1230 pretty-printing and hashkey sorting enabled, JSON::XS/3 enables shrink.
837 Higher is better: 1231 JSON::DWIW/DS uses the deserialise function, while JSON::DWIW::FJ uses
1232 the from_json method). Higher is better:
838 1233
839 module | encode | decode | 1234 module | encode | decode |
840 -----------|------------|------------| 1235 --------------|------------|------------|
841 JSON 1.x | 4990.842 | 4088.813 | 1236 JSON::DWIW/DS | 86302.551 | 102300.098 |
842 JSON::DWIW | 51653.990 | 71575.154 | 1237 JSON::DWIW/FJ | 86302.551 | 75983.768 |
843 JSON::PC | 65948.176 | 74631.744 | 1238 JSON::PP | 15827.562 | 6638.658 |
844 JSON::PP | 8931.652 | 3817.168 | 1239 JSON::Syck | 63358.066 | 47662.545 |
845 JSON::Syck | 24877.248 | 27776.848 | 1240 JSON::XS | 511500.488 | 511500.488 |
846 JSON::XS | 388361.481 | 227951.304 | 1241 JSON::XS/2 | 291271.111 | 388361.481 |
847 JSON::XS/2 | 227951.304 | 218453.333 | 1242 JSON::XS/3 | 361577.931 | 361577.931 |
848 JSON::XS/3 | 338250.323 | 218453.333 | 1243 Storable | 66788.280 | 265462.278 |
849 Storable | 16500.016 | 135300.129 |
850 -----------+------------+------------+ 1244 --------------+------------+------------+
851 1245
852 That is, JSON::XS is about five times faster than JSON::DWIW on 1246 That is, JSON::XS is almost six times faster than JSON::DWIW on
853 encoding, about three times faster on decoding, and over forty times 1247 encoding, about five times faster on decoding, and over thirty to
854 faster than JSON, even with pretty-printing and key sorting. It also 1248 seventy times faster than JSON's pure perl implementation. It also
855 compares favourably to Storable for small amounts of data. 1249 compares favourably to Storable for small amounts of data.
856 1250
857 Using a longer test string (roughly 18KB, generated from Yahoo! Locals 1251 Using a longer test string (roughly 18KB, generated from Yahoo! Locals
858 search API (http://nanoref.com/yahooapis/mgPdGg): 1252 search API (<http://dist.schmorp.de/misc/json/long.json>).
859 1253
860 module | encode | decode | 1254 module | encode | decode |
861 -----------|------------|------------| 1255 --------------|------------|------------|
862 JSON 1.x | 55.260 | 34.971 | 1256 JSON::DWIW/DS | 1647.927 | 2673.916 |
863 JSON::DWIW | 825.228 | 1082.513 | 1257 JSON::DWIW/FJ | 1630.249 | 2596.128 |
864 JSON::PC | 3571.444 | 2394.829 |
865 JSON::PP | 210.987 | 32.574 | 1258 JSON::PP | 400.640 | 62.311 |
866 JSON::Syck | 552.551 | 787.544 | 1259 JSON::Syck | 1481.040 | 1524.869 |
867 JSON::XS | 5780.463 | 4854.519 | 1260 JSON::XS | 20661.596 | 9541.183 |
868 JSON::XS/2 | 3869.998 | 4798.975 | 1261 JSON::XS/2 | 10683.403 | 9416.938 |
869 JSON::XS/3 | 5862.880 | 4798.975 | 1262 JSON::XS/3 | 20661.596 | 9400.054 |
870 Storable | 4445.002 | 5235.027 | 1263 Storable | 19765.806 | 10000.725 |
871 -----------+------------+------------+ 1264 --------------+------------+------------+
872 1265
873 Again, JSON::XS leads by far (except for Storable which non-surprisingly 1266 Again, JSON::XS leads by far (except for Storable which non-surprisingly
874 decodes faster). 1267 decodes a bit faster).
875 1268
876 On large strings containing lots of high Unicode characters, some 1269 On large strings containing lots of high Unicode characters, some
877 modules (such as JSON::PC) seem to decode faster than JSON::XS, but the 1270 modules (such as JSON::PC) seem to decode faster than JSON::XS, but the
878 result will be broken due to missing (or wrong) Unicode handling. Others 1271 result will be broken due to missing (or wrong) Unicode handling. Others
879 refuse to decode or encode properly, so it was impossible to prepare a 1272 refuse to decode or encode properly, so it was impossible to prepare a
… …
900 Third, JSON::XS recurses using the C stack when decoding objects and 1293 Third, JSON::XS recurses using the C stack when decoding objects and
901 arrays. The C stack is a limited resource: for instance, on my amd64 1294 arrays. The C stack is a limited resource: for instance, on my amd64
902 machine with 8MB of stack size I can decode around 180k nested arrays 1295 machine with 8MB of stack size I can decode around 180k nested arrays
903 but only 14k nested JSON objects (due to perl itself recursing deeply on 1296 but only 14k nested JSON objects (due to perl itself recursing deeply on
904 croak to free the temporary). If that is exceeded, the program crashes. 1297 croak to free the temporary). If that is exceeded, the program crashes.
905 to be conservative, the default nesting limit is set to 512. If your 1298 To be conservative, the default nesting limit is set to 512. If your
906 process has a smaller stack, you should adjust this setting accordingly 1299 process has a smaller stack, you should adjust this setting accordingly
907 with the "max_depth" method. 1300 with the "max_depth" method.
908 1301
909 And last but least, something else could bomb you that I forgot to think 1302 Something else could bomb you, too, that I forgot to think of. In that
910 of. In that case, you get to keep the pieces. I am always open for 1303 case, you get to keep the pieces. I am always open for hints, though...
911 hints, though... 1304
1305 Also keep in mind that JSON::XS might leak contents of your Perl data
1306 structures in its error messages, so when you serialise sensitive
1307 information you might want to make sure that exceptions thrown by
1308 JSON::XS will not end up in front of untrusted eyes.
912 1309
913 If you are using JSON::XS to return packets to consumption by JavaScript 1310 If you are using JSON::XS to return packets to consumption by JavaScript
914 scripts in a browser you should have a look at 1311 scripts in a browser you should have a look at
915 <http://jpsykes.com/47/practical-csrf-and-json-security> to see whether 1312 <http://blog.archive.jpsykes.com/47/practical-csrf-and-json-security/>
916 you are vulnerable to some common attack vectors (which really are 1313 to see whether you are vulnerable to some common attack vectors (which
917 browser design bugs, but it is still you who will have to deal with it, 1314 really are browser design bugs, but it is still you who will have to
918 as major browser developers care only for features, not about doing 1315 deal with it, as major browser developers care only for features, not
919 security right). 1316 about getting security right).
920 1317
921THREADS 1318THREADS
922 This module is *not* guaranteed to be thread safe and there are no plans 1319 This module is *not* guaranteed to be thread safe and there are no plans
923 to change this until Perl gets thread support (as opposed to the 1320 to change this until Perl gets thread support (as opposed to the
924 horribly slow so-called "threads" which are simply slow and bloated 1321 horribly slow so-called "threads" which are simply slow and bloated
925 process simulations - use fork, its *much* faster, cheaper, better). 1322 process simulations - use fork, it's *much* faster, cheaper, better).
926 1323
927 (It might actually work, but you have been warned). 1324 (It might actually work, but you have been warned).
1325
1326THE PERILS OF SETLOCALE
1327 Sometimes people avoid the Perl locale support and directly call the
1328 system's setlocale function with "LC_ALL".
1329
1330 This breaks both perl and modules such as JSON::XS, as stringification
1331 of numbers no longer works correcly (e.g. "$x = 0.1; print "$x"+1" might
1332 print 1, and JSON::XS might output illegal JSON as JSON::XS relies on
1333 perl to stringify numbers).
1334
1335 The solution is simple: don't call "setlocale", or use it for only those
1336 categories you need, such as "LC_MESSAGES" or "LC_CTYPE".
1337
1338 If you need "LC_NUMERIC", you should enable it only around the code that
1339 actually needs it (avoiding stringification of numbers), and restore it
1340 afterwards.
928 1341
929BUGS 1342BUGS
930 While the goal of this module is to be correct, that unfortunately does 1343 While the goal of this module is to be correct, that unfortunately does
931 not mean its bug-free, only that I think its design is bug-free. It is 1344 not mean it's bug-free, only that I think its design is bug-free. If you
932 still relatively early in its development. If you keep reporting bugs
933 they will be fixed swiftly, though. 1345 keep reporting bugs they will be fixed swiftly, though.
934 1346
935 Please refrain from using rt.cpan.org or any other bug reporting 1347 Please refrain from using rt.cpan.org or any other bug reporting
936 service. I put the contact address into my modules for a reason. 1348 service. I put the contact address into my modules for a reason.
1349
1350SEE ALSO
1351 The json_xs command line utility for quick experiments.
937 1352
938AUTHOR 1353AUTHOR
939 Marc Lehmann <schmorp@schmorp.de> 1354 Marc Lehmann <schmorp@schmorp.de>
940 http://home.schmorp.de/ 1355 http://home.schmorp.de/
941 1356

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines