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

Comparing JSON-XS/README (file contents):
Revision 1.14 by root, Sat Jun 23 23:50:03 2007 UTC vs.
Revision 1.20 by root, Tue Nov 13 22:59:08 2007 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
5 シリアライザ/デシリアライザ
6 (http://fleur.hio.jp/perldoc/mix/lib/JSON/XS.html)
7
4SYNOPSIS 8SYNOPSIS
5 use JSON::XS; 9 use JSON::XS;
6 10
7 # exported functions, they croak on error 11 # exported functions, they croak on error
8 # and expect/generate UTF-8 12 # and expect/generate UTF-8
9 13
10 $utf8_encoded_json_text = to_json $perl_hash_or_arrayref; 14 $utf8_encoded_json_text = to_json $perl_hash_or_arrayref;
11 $perl_hash_or_arrayref = from_json $utf8_encoded_json_text; 15 $perl_hash_or_arrayref = from_json $utf8_encoded_json_text;
12
13 # objToJson and jsonToObj aliases to to_json and from_json
14 # are exported for compatibility to the JSON module,
15 # but should not be used in new code.
16 16
17 # OO-interface 17 # OO-interface
18 18
19 $coder = JSON::XS->new->ascii->pretty->allow_nonref; 19 $coder = JSON::XS->new->ascii->pretty->allow_nonref;
20 $pretty_printed_unencoded = $coder->encode ($perl_scalar); 20 $pretty_printed_unencoded = $coder->encode ($perl_scalar);
… …
35 35
36 See MAPPING, below, on how JSON::XS maps perl values to JSON values and 36 See MAPPING, below, on how JSON::XS maps perl values to JSON values and
37 vice versa. 37 vice versa.
38 38
39 FEATURES 39 FEATURES
40 * correct unicode handling 40 * correct Unicode handling
41 This module knows how to handle Unicode, and even documents how and 41 This module knows how to handle Unicode, and even documents how and
42 when it does so. 42 when it does so.
43 43
44 * round-trip integrity 44 * round-trip integrity
45 When you serialise a perl data structure using only datatypes 45 When you serialise a perl data structure using only datatypes
… …
59 * simple to use 59 * simple to use
60 This module has both a simple functional interface as well as an OO 60 This module has both a simple functional interface as well as an OO
61 interface. 61 interface.
62 62
63 * reasonably versatile output formats 63 * reasonably versatile output formats
64 You can choose between the most compact guarenteed single-line 64 You can choose between the most compact guaranteed single-line
65 format possible (nice for simple line-based protocols), a pure-ascii 65 format possible (nice for simple line-based protocols), a pure-ascii
66 format (for when your transport is not 8-bit clean, still supports 66 format (for when your transport is not 8-bit clean, still supports
67 the whole unicode range), or a pretty-printed format (for when you 67 the whole Unicode range), or a pretty-printed format (for when you
68 want to read that stuff). Or you can combine those features in 68 want to read that stuff). Or you can combine those features in
69 whatever way you like. 69 whatever way you like.
70 70
71FUNCTIONAL INTERFACE 71FUNCTIONAL INTERFACE
72 The following convinience methods are provided by this module. They are 72 The following convenience methods are provided by this module. They are
73 exported by default: 73 exported by default:
74 74
75 $json_text = to_json $perl_scalar 75 $json_text = to_json $perl_scalar
76 Converts the given Perl data structure (a simple scalar or a 76 Converts the given Perl data structure to a UTF-8 encoded, binary
77 reference to a hash or array) to a UTF-8 encoded, binary string
78 (that is, the string contains octets only). Croaks on error. 77 string (that is, the string contains octets only). Croaks on error.
79 78
80 This function call is functionally identical to: 79 This function call is functionally identical to:
81 80
82 $json_text = JSON::XS->new->utf8->encode ($perl_scalar) 81 $json_text = JSON::XS->new->utf8->encode ($perl_scalar)
83 82
84 except being faster. 83 except being faster.
85 84
86 $perl_scalar = from_json $json_text 85 $perl_scalar = from_json $json_text
87 The opposite of "to_json": expects an UTF-8 (binary) string and 86 The opposite of "to_json": expects an UTF-8 (binary) string and
88 tries to parse that as an UTF-8 encoded JSON text, returning the 87 tries to parse that as an UTF-8 encoded JSON text, returning the
89 resulting simple scalar or reference. Croaks on error. 88 resulting reference. Croaks on error.
90 89
91 This function call is functionally identical to: 90 This function call is functionally identical to:
92 91
93 $perl_scalar = JSON::XS->new->utf8->decode ($json_text) 92 $perl_scalar = JSON::XS->new->utf8->decode ($json_text)
94 93
… …
101 values in Perl. 100 values in Perl.
102 101
103 See MAPPING, below, for more information on how JSON values are 102 See MAPPING, below, for more information on how JSON values are
104 mapped to Perl. 103 mapped to Perl.
105 104
105A FEW NOTES ON UNICODE AND PERL
106 Since this often leads to confusion, here are a few very clear words on
107 how Unicode works in Perl, modulo bugs.
108
109 1. Perl strings can store characters with ordinal values > 255.
110 This enables you to store Unicode characters as single characters in
111 a Perl string - very natural.
112
113 2. Perl does *not* associate an encoding with your strings.
114 Unless you force it to, e.g. when matching it against a regex, or
115 printing the scalar to a file, in which case Perl either interprets
116 your string as locale-encoded text, octets/binary, or as Unicode,
117 depending on various settings. In no case is an encoding stored
118 together with your data, it is *use* that decides encoding, not any
119 magical metadata.
120
121 3. The internal utf-8 flag has no meaning with regards to the encoding
122 of your string.
123 Just ignore that flag unless you debug a Perl bug, a module written
124 in XS or want to dive into the internals of perl. Otherwise it will
125 only confuse you, as, despite the name, it says nothing about how
126 your string is encoded. You can have Unicode strings with that flag
127 set, with that flag clear, and you can have binary data with that
128 flag set and that flag clear. Other possibilities exist, too.
129
130 If you didn't know about that flag, just the better, pretend it
131 doesn't exist.
132
133 4. A "Unicode String" is simply a string where each character can be
134 validly interpreted as a Unicode codepoint.
135 If you have UTF-8 encoded data, it is no longer a Unicode string,
136 but a Unicode string encoded in UTF-8, giving you a binary string.
137
138 5. A string containing "high" (> 255) character values is *not* a UTF-8
139 string.
140 It's a fact. Learn to live with it.
141
142 I hope this helps :)
143
106OBJECT-ORIENTED INTERFACE 144OBJECT-ORIENTED INTERFACE
107 The object oriented interface lets you configure your own encoding or 145 The object oriented interface lets you configure your own encoding or
108 decoding style, within the limits of supported formats. 146 decoding style, within the limits of supported formats.
109 147
110 $json = new JSON::XS 148 $json = new JSON::XS
… …
119 => {"a": [1, 2]} 157 => {"a": [1, 2]}
120 158
121 $json = $json->ascii ([$enable]) 159 $json = $json->ascii ([$enable])
122 If $enable is true (or missing), then the "encode" method will not 160 If $enable is true (or missing), then the "encode" method will not
123 generate characters outside the code range 0..127 (which is ASCII). 161 generate characters outside the code range 0..127 (which is ASCII).
124 Any unicode characters outside that range will be escaped using 162 Any Unicode characters outside that range will be escaped using
125 either a single \uXXXX (BMP characters) or a double \uHHHH\uLLLLL 163 either a single \uXXXX (BMP characters) or a double \uHHHH\uLLLLL
126 escape sequence, as per RFC4627. The resulting encoded JSON text can 164 escape sequence, as per RFC4627. The resulting encoded JSON text can
127 be treated as a native unicode string, an ascii-encoded, 165 be treated as a native Unicode string, an ascii-encoded,
128 latin1-encoded or UTF-8 encoded string, or any other superset of 166 latin1-encoded or UTF-8 encoded string, or any other superset of
129 ASCII. 167 ASCII.
130 168
131 If $enable is false, then the "encode" method will not escape 169 If $enable is false, then the "encode" method will not escape
132 Unicode characters unless required by the JSON syntax or other 170 Unicode characters unless required by the JSON syntax or other
… …
141 179
142 $json = $json->latin1 ([$enable]) 180 $json = $json->latin1 ([$enable])
143 If $enable is true (or missing), then the "encode" method will 181 If $enable is true (or missing), then the "encode" method will
144 encode the resulting JSON text as latin1 (or iso-8859-1), escaping 182 encode the resulting JSON text as latin1 (or iso-8859-1), escaping
145 any characters outside the code range 0..255. The resulting string 183 any characters outside the code range 0..255. The resulting string
146 can be treated as a latin1-encoded JSON text or a native unicode 184 can be treated as a latin1-encoded JSON text or a native Unicode
147 string. The "decode" method will not be affected in any way by this 185 string. The "decode" method will not be affected in any way by this
148 flag, as "decode" by default expects unicode, which is a strict 186 flag, as "decode" by default expects Unicode, which is a strict
149 superset of latin1. 187 superset of latin1.
150 188
151 If $enable is false, then the "encode" method will not escape 189 If $enable is false, then the "encode" method will not escape
152 Unicode characters unless required by the JSON syntax or other 190 Unicode characters unless required by the JSON syntax or other
153 flags. 191 flags.
154 192
155 The main use for this flag is efficiently encoding binary data as 193 The main use for this flag is efficiently encoding binary data as
156 JSON text, as most octets will not be escaped, resulting in a 194 JSON text, as most octets will not be escaped, resulting in a
157 smaller encoded size. The disadvantage is that the resulting JSON 195 smaller encoded size. The disadvantage is that the resulting JSON
158 text is encoded in latin1 (and must correctly be treated as such 196 text is encoded in latin1 (and must correctly be treated as such
159 when storing and transfering), a rare encoding for JSON. It is 197 when storing and transferring), a rare encoding for JSON. It is
160 therefore most useful when you want to store data structures known 198 therefore most useful when you want to store data structures known
161 to contain binary data efficiently in files or databases, not when 199 to contain binary data efficiently in files or databases, not when
162 talking to other JSON encoders/decoders. 200 talking to other JSON encoders/decoders.
163 201
164 JSON::XS->new->latin1->encode (["\x{89}\x{abc}"] 202 JSON::XS->new->latin1->encode (["\x{89}\x{abc}"]
… …
173 bytewise/binary I/O. In future versions, enabling this option might 211 bytewise/binary I/O. In future versions, enabling this option might
174 enable autodetection of the UTF-16 and UTF-32 encoding families, as 212 enable autodetection of the UTF-16 and UTF-32 encoding families, as
175 described in RFC4627. 213 described in RFC4627.
176 214
177 If $enable is false, then the "encode" method will return the JSON 215 If $enable is false, then the "encode" method will return the JSON
178 string as a (non-encoded) unicode string, while "decode" expects 216 string as a (non-encoded) Unicode string, while "decode" expects
179 thus a unicode string. Any decoding or encoding (e.g. to UTF-8 or 217 thus a Unicode string. Any decoding or encoding (e.g. to UTF-8 or
180 UTF-16) needs to be done yourself, e.g. using the Encode module. 218 UTF-16) needs to be done yourself, e.g. using the Encode module.
181 219
182 Example, output UTF-16BE-encoded JSON: 220 Example, output UTF-16BE-encoded JSON:
183 221
184 use Encode; 222 use Encode;
… …
206 } 244 }
207 245
208 $json = $json->indent ([$enable]) 246 $json = $json->indent ([$enable])
209 If $enable is true (or missing), then the "encode" method will use a 247 If $enable is true (or missing), then the "encode" method will use a
210 multiline format as output, putting every array member or 248 multiline format as output, putting every array member or
211 object/hash key-value pair into its own line, identing them 249 object/hash key-value pair into its own line, indenting them
212 properly. 250 properly.
213 251
214 If $enable is false, no newlines or indenting will be produced, and 252 If $enable is false, no newlines or indenting will be produced, and
215 the resulting JSON text is guarenteed not to contain any "newlines". 253 the resulting JSON text is guaranteed not to contain any "newlines".
216 254
217 This setting has no effect when decoding JSON texts. 255 This setting has no effect when decoding JSON texts.
218 256
219 $json = $json->space_before ([$enable]) 257 $json = $json->space_before ([$enable])
220 If $enable is true (or missing), then the "encode" method will add 258 If $enable is true (or missing), then the "encode" method will add
… …
244 282
245 Example, space_before and indent disabled, space_after enabled: 283 Example, space_before and indent disabled, space_after enabled:
246 284
247 {"key": "value"} 285 {"key": "value"}
248 286
287 $json = $json->relaxed ([$enable])
288 If $enable is true (or missing), then "decode" will accept some
289 extensions to normal JSON syntax (see below). "encode" will not be
290 affected in anyway. *Be aware that this option makes you accept
291 invalid JSON texts as if they were valid!*. I suggest only to use
292 this option to parse application-specific files written by humans
293 (configuration files, resource files etc.)
294
295 If $enable is false (the default), then "decode" will only accept
296 valid JSON texts.
297
298 Currently accepted extensions are:
299
300 * list items can have an end-comma
301 JSON *separates* array elements and key-value pairs with commas.
302 This can be annoying if you write JSON texts manually and want
303 to be able to quickly append elements, so this extension accepts
304 comma at the end of such items not just between them:
305
306 [
307 1,
308 2, <- this comma not normally allowed
309 ]
310 {
311 "k1": "v1",
312 "k2": "v2", <- this comma not normally allowed
313 }
314
315 * shell-style '#'-comments
316 Whenever JSON allows whitespace, shell-style comments are
317 additionally allowed. They are terminated by the first
318 carriage-return or line-feed character, after which more
319 white-space and comments are allowed.
320
321 [
322 1, # this comment not allowed in JSON
323 # neither this one...
324 ]
325
249 $json = $json->canonical ([$enable]) 326 $json = $json->canonical ([$enable])
250 If $enable is true (or missing), then the "encode" method will 327 If $enable is true (or missing), then the "encode" method will
251 output JSON objects by sorting their keys. This is adding a 328 output JSON objects by sorting their keys. This is adding a
252 comparatively high overhead. 329 comparatively high overhead.
253 330
… …
255 pairs in the order Perl stores them (which will likely change 332 pairs in the order Perl stores them (which will likely change
256 between runs of the same script). 333 between runs of the same script).
257 334
258 This option is useful if you want the same data structure to be 335 This option is useful if you want the same data structure to be
259 encoded as the same JSON text (given the same overall settings). If 336 encoded as the same JSON text (given the same overall settings). If
260 it is disabled, the same hash migh be encoded differently even if 337 it is disabled, the same hash might be encoded differently even if
261 contains the same data, as key-value pairs have no inherent ordering 338 contains the same data, as key-value pairs have no inherent ordering
262 in Perl. 339 in Perl.
263 340
264 This setting has no effect when decoding JSON texts. 341 This setting has no effect when decoding JSON texts.
265 342
… …
277 Example, encode a Perl scalar as JSON value with enabled 354 Example, encode a Perl scalar as JSON value with enabled
278 "allow_nonref", resulting in an invalid JSON text: 355 "allow_nonref", resulting in an invalid JSON text:
279 356
280 JSON::XS->new->allow_nonref->encode ("Hello, World!") 357 JSON::XS->new->allow_nonref->encode ("Hello, World!")
281 => "Hello, World!" 358 => "Hello, World!"
359
360 $json = $json->allow_blessed ([$enable])
361 If $enable is true (or missing), then the "encode" method will not
362 barf when it encounters a blessed reference. Instead, the value of
363 the convert_blessed option will decide whether "null"
364 ("convert_blessed" disabled or no "to_json" method found) or a
365 representation of the object ("convert_blessed" enabled and
366 "to_json" method found) is being encoded. Has no effect on "decode".
367
368 If $enable is false (the default), then "encode" will throw an
369 exception when it encounters a blessed object.
370
371 $json = $json->convert_blessed ([$enable])
372 If $enable is true (or missing), then "encode", upon encountering a
373 blessed object, will check for the availability of the "TO_JSON"
374 method on the object's class. If found, it will be called in scalar
375 context and the resulting scalar will be encoded instead of the
376 object. If no "TO_JSON" method is found, the value of
377 "allow_blessed" will decide what to do.
378
379 The "TO_JSON" method may safely call die if it wants. If "TO_JSON"
380 returns other blessed objects, those will be handled in the same
381 way. "TO_JSON" must take care of not causing an endless recursion
382 cycle (== crash) in this case. The name of "TO_JSON" was chosen
383 because other methods called by the Perl core (== not by the user of
384 the object) are usually in upper case letters and to avoid
385 collisions with the "to_json" function.
386
387 This setting does not yet influence "decode" in any way, but in the
388 future, global hooks might get installed that influence "decode" and
389 are enabled by this setting.
390
391 If $enable is false, then the "allow_blessed" setting will decide
392 what to do when a blessed object is found.
393
394 $json = $json->filter_json_object ([$coderef->($hashref)])
395 When $coderef is specified, it will be called from "decode" each
396 time it decodes a JSON object. The only argument is a reference to
397 the newly-created hash. If the code references returns a single
398 scalar (which need not be a reference), this value (i.e. a copy of
399 that scalar to avoid aliasing) is inserted into the deserialised
400 data structure. If it returns an empty list (NOTE: *not* "undef",
401 which is a valid scalar), the original deserialised hash will be
402 inserted. This setting can slow down decoding considerably.
403
404 When $coderef is omitted or undefined, any existing callback will be
405 removed and "decode" will not change the deserialised hash in any
406 way.
407
408 Example, convert all JSON objects into the integer 5:
409
410 my $js = JSON::XS->new->filter_json_object (sub { 5 });
411 # returns [5]
412 $js->decode ('[{}]')
413 # throw an exception because allow_nonref is not enabled
414 # so a lone 5 is not allowed.
415 $js->decode ('{"a":1, "b":2}');
416
417 $json = $json->filter_json_single_key_object ($key [=>
418 $coderef->($value)])
419 Works remotely similar to "filter_json_object", but is only called
420 for JSON objects having a single key named $key.
421
422 This $coderef is called before the one specified via
423 "filter_json_object", if any. It gets passed the single value in the
424 JSON object. If it returns a single value, it will be inserted into
425 the data structure. If it returns nothing (not even "undef" but the
426 empty list), the callback from "filter_json_object" will be called
427 next, as if no single-key callback were specified.
428
429 If $coderef is omitted or undefined, the corresponding callback will
430 be disabled. There can only ever be one callback for a given key.
431
432 As this callback gets called less often then the
433 "filter_json_object" one, decoding speed will not usually suffer as
434 much. Therefore, single-key objects make excellent targets to
435 serialise Perl objects into, especially as single-key JSON objects
436 are as close to the type-tagged value concept as JSON gets (it's
437 basically an ID/VALUE tuple). Of course, JSON does not support this
438 in any way, so you need to make sure your data never looks like a
439 serialised Perl hash.
440
441 Typical names for the single object key are "__class_whatever__", or
442 "$__dollars_are_rarely_used__$" or "}ugly_brace_placement", or even
443 things like "__class_md5sum(classname)__", to reduce the risk of
444 clashing with real hashes.
445
446 Example, decode JSON objects of the form "{ "__widget__" => <id> }"
447 into the corresponding $WIDGET{<id>} object:
448
449 # return whatever is in $WIDGET{5}:
450 JSON::XS
451 ->new
452 ->filter_json_single_key_object (__widget__ => sub {
453 $WIDGET{ $_[0] }
454 })
455 ->decode ('{"__widget__": 5')
456
457 # this can be used with a TO_JSON method in some "widget" class
458 # for serialisation to json:
459 sub WidgetBase::TO_JSON {
460 my ($self) = @_;
461
462 unless ($self->{id}) {
463 $self->{id} = ..get..some..id..;
464 $WIDGET{$self->{id}} = $self;
465 }
466
467 { __widget__ => $self->{id} }
468 }
282 469
283 $json = $json->shrink ([$enable]) 470 $json = $json->shrink ([$enable])
284 Perl usually over-allocates memory a bit when allocating space for 471 Perl usually over-allocates memory a bit when allocating space for
285 strings. This flag optionally resizes strings generated by either 472 strings. This flag optionally resizes strings generated by either
286 "encode" or "decode" to their minimum size possible. This can save 473 "encode" or "decode" to their minimum size possible. This can save
… …
319 crossed to reach a given character in a string. 506 crossed to reach a given character in a string.
320 507
321 Setting the maximum depth to one disallows any nesting, so that 508 Setting the maximum depth to one disallows any nesting, so that
322 ensures that the object is only a single hash/object or array. 509 ensures that the object is only a single hash/object or array.
323 510
324 The argument to "max_depth" will be rounded up to the next nearest 511 The argument to "max_depth" will be rounded up to the next highest
325 power of two. 512 power of two. If no argument is given, the highest possible setting
513 will be used, which is rarely useful.
514
515 See SECURITY CONSIDERATIONS, below, for more info on why this is
516 useful.
517
518 $json = $json->max_size ([$maximum_string_size])
519 Set the maximum length a JSON text may have (in bytes) where
520 decoding is being attempted. The default is 0, meaning no limit.
521 When "decode" is called on a string longer then this number of
522 characters it will not attempt to decode the string but throw an
523 exception. This setting has no effect on "encode" (yet).
524
525 The argument to "max_size" will be rounded up to the next highest
526 power of two (so may be more than requested). If no argument is
527 given, the limit check will be deactivated (same as when 0 is
528 specified).
326 529
327 See SECURITY CONSIDERATIONS, below, for more info on why this is 530 See SECURITY CONSIDERATIONS, below, for more info on why this is
328 useful. 531 useful.
329 532
330 $json_text = $json->encode ($perl_scalar) 533 $json_text = $json->encode ($perl_scalar)
… …
362 vice versa. These mappings are designed to "do the right thing" in most 565 vice versa. These mappings are designed to "do the right thing" in most
363 circumstances automatically, preserving round-tripping characteristics 566 circumstances automatically, preserving round-tripping characteristics
364 (what you put in comes out as something equivalent). 567 (what you put in comes out as something equivalent).
365 568
366 For the more enlightened: note that in the following descriptions, 569 For the more enlightened: note that in the following descriptions,
367 lowercase *perl* refers to the Perl interpreter, while uppcercase *Perl* 570 lowercase *perl* refers to the Perl interpreter, while uppercase *Perl*
368 refers to the abstract Perl language itself. 571 refers to the abstract Perl language itself.
369 572
370 JSON -> PERL 573 JSON -> PERL
371 object 574 object
372 A JSON object becomes a reference to a hash in Perl. No ordering of 575 A JSON object becomes a reference to a hash in Perl. No ordering of
373 object keys is preserved (JSON does not preserver object key 576 object keys is preserved (JSON does not preserve object key ordering
374 ordering itself). 577 itself).
375 578
376 array 579 array
377 A JSON array becomes a reference to an array in Perl. 580 A JSON array becomes a reference to an array in Perl.
378 581
379 string 582 string
380 A JSON string becomes a string scalar in Perl - Unicode codepoints 583 A JSON string becomes a string scalar in Perl - Unicode codepoints
381 in JSON are represented by the same codepoints in the Perl string, 584 in JSON are represented by the same codepoints in the Perl string,
382 so no manual decoding is necessary. 585 so no manual decoding is necessary.
383 586
384 number 587 number
385 A JSON number becomes either an integer or numeric (floating point) 588 A JSON number becomes either an integer, numeric (floating point) or
386 scalar in perl, depending on its range and any fractional parts. On 589 string scalar in perl, depending on its range and any fractional
387 the Perl level, there is no difference between those as Perl handles 590 parts. On the Perl level, there is no difference between those as
388 all the conversion details, but an integer may take slightly less 591 Perl handles all the conversion details, but an integer may take
389 memory and might represent more values exactly than (floating point) 592 slightly less memory and might represent more values exactly than
390 numbers. 593 (floating point) numbers.
594
595 If the number consists of digits only, JSON::XS will try to
596 represent it as an integer value. If that fails, it will try to
597 represent it as a numeric (floating point) value if that is possible
598 without loss of precision. Otherwise it will preserve the number as
599 a string value.
600
601 Numbers containing a fractional or exponential part will always be
602 represented as numeric (floating point) values, possibly at a loss
603 of precision.
604
605 This might create round-tripping problems as numbers might become
606 strings, but as Perl is typeless there is no other way to do it.
391 607
392 true, false 608 true, false
393 These JSON atoms become "JSON::XS::true" and "JSON::XS::false", 609 These JSON atoms become "JSON::XS::true" and "JSON::XS::false",
394 respectively. They are overloaded to act almost exactly like the 610 respectively. They are overloaded to act almost exactly like the
395 numbers 1 and 0. You can check wether a scalar is a JSON boolean by 611 numbers 1 and 0. You can check whether a scalar is a JSON boolean by
396 using the "JSON::XS::is_bool" function. 612 using the "JSON::XS::is_bool" function.
397 613
398 null 614 null
399 A JSON null atom becomes "undef" in Perl. 615 A JSON null atom becomes "undef" in Perl.
400 616
… …
427 643
428 to_json [\0,JSON::XS::true] # yields [false,true] 644 to_json [\0,JSON::XS::true] # yields [false,true]
429 645
430 JSON::XS::true, JSON::XS::false 646 JSON::XS::true, JSON::XS::false
431 These special values become JSON true and JSON false values, 647 These special values become JSON true and JSON false values,
432 respectively. You cna alos use "\1" and "\0" directly if you want. 648 respectively. You can also use "\1" and "\0" directly if you want.
433 649
434 blessed objects 650 blessed objects
435 Blessed objects are not allowed. JSON::XS currently tries to encode 651 Blessed objects are not allowed. JSON::XS currently tries to encode
436 their underlying representation (hash- or arrayref), but this 652 their underlying representation (hash- or arrayref), but this
437 behaviour might change in future versions. 653 behaviour might change in future versions.
… …
453 to_json [$value] # yields ["5"] 669 to_json [$value] # yields ["5"]
454 670
455 # undef becomes null 671 # undef becomes null
456 to_json [undef] # yields [null] 672 to_json [undef] # yields [null]
457 673
458 You can force the type to be a string by stringifying it: 674 You can force the type to be a JSON string by stringifying it:
459 675
460 my $x = 3.1; # some variable containing a number 676 my $x = 3.1; # some variable containing a number
461 "$x"; # stringified 677 "$x"; # stringified
462 $x .= ""; # another, more awkward way to stringify 678 $x .= ""; # another, more awkward way to stringify
463 print $x; # perl does it for you, too, quite often 679 print $x; # perl does it for you, too, quite often
464 680
465 You can force the type to be a number by numifying it: 681 You can force the type to be a JSON number by numifying it:
466 682
467 my $x = "3"; # some variable containing a string 683 my $x = "3"; # some variable containing a string
468 $x += 0; # numify it, ensuring it will be dumped as a number 684 $x += 0; # numify it, ensuring it will be dumped as a number
469 $x *= 1; # same thing, the choise is yours. 685 $x *= 1; # same thing, the choice is yours.
470 686
471 You can not currently output JSON booleans or force the type in 687 You can not currently force the type in other, less obscure, ways.
472 other, less obscure, ways. Tell me if you need this capability. 688 Tell me if you need this capability.
473 689
474COMPARISON 690COMPARISON
475 As already mentioned, this module was created because none of the 691 As already mentioned, this module was created because none of the
476 existing JSON modules could be made to work correctly. First I will 692 existing JSON modules could be made to work correctly. First I will
477 describe the problems (or pleasures) I encountered with various existing 693 describe the problems (or pleasures) I encountered with various existing
… …
479 not to suffer from any of these problems or limitations. 695 not to suffer from any of these problems or limitations.
480 696
481 JSON 1.07 697 JSON 1.07
482 Slow (but very portable, as it is written in pure Perl). 698 Slow (but very portable, as it is written in pure Perl).
483 699
484 Undocumented/buggy Unicode handling (how JSON handles unicode values 700 Undocumented/buggy Unicode handling (how JSON handles Unicode values
485 is undocumented. One can get far by feeding it unicode strings and 701 is undocumented. One can get far by feeding it Unicode strings and
486 doing en-/decoding oneself, but unicode escapes are not working 702 doing en-/decoding oneself, but Unicode escapes are not working
487 properly). 703 properly).
488 704
489 No roundtripping (strings get clobbered if they look like numbers, 705 No round-tripping (strings get clobbered if they look like numbers,
490 e.g. the string 2.0 will encode to 2.0 instead of "2.0", and that 706 e.g. the string 2.0 will encode to 2.0 instead of "2.0", and that
491 will decode into the number 2. 707 will decode into the number 2.
492 708
493 JSON::PC 0.01 709 JSON::PC 0.01
494 Very fast. 710 Very fast.
495 711
496 Undocumented/buggy Unicode handling. 712 Undocumented/buggy Unicode handling.
497 713
498 No roundtripping. 714 No round-tripping.
499 715
500 Has problems handling many Perl values (e.g. regex results and other 716 Has problems handling many Perl values (e.g. regex results and other
501 magic values will make it croak). 717 magic values will make it croak).
502 718
503 Does not even generate valid JSON ("{1,2}" gets converted to "{1:2}" 719 Does not even generate valid JSON ("{1,2}" gets converted to "{1:2}"
… …
513 much undocumented. I need at least a format for easy reading by 729 much undocumented. I need at least a format for easy reading by
514 humans and a single-line compact format for use in a protocol, and 730 humans and a single-line compact format for use in a protocol, and
515 preferably a way to generate ASCII-only JSON texts). 731 preferably a way to generate ASCII-only JSON texts).
516 732
517 Completely broken (and confusingly documented) Unicode handling 733 Completely broken (and confusingly documented) Unicode handling
518 (unicode escapes are not working properly, you need to set 734 (Unicode escapes are not working properly, you need to set
519 ImplicitUnicode to *different* values on en- and decoding to get 735 ImplicitUnicode to *different* values on en- and decoding to get
520 symmetric behaviour). 736 symmetric behaviour).
521 737
522 No roundtripping (simple cases work, but this depends on wether the 738 No round-tripping (simple cases work, but this depends on whether
523 scalar value was used in a numeric context or not). 739 the scalar value was used in a numeric context or not).
524 740
525 Dumping hashes may skip hash values depending on iterator state. 741 Dumping hashes may skip hash values depending on iterator state.
526 742
527 Unmaintained (maintainer unresponsive for many months, bugs are not 743 Unmaintained (maintainer unresponsive for many months, bugs are not
528 getting fixed). 744 getting fixed).
529 745
530 Does not check input for validity (i.e. will accept non-JSON input 746 Does not check input for validity (i.e. will accept non-JSON input
531 and return "something" instead of raising an exception. This is a 747 and return "something" instead of raising an exception. This is a
532 security issue: imagine two banks transfering money between each 748 security issue: imagine two banks transferring money between each
533 other using JSON. One bank might parse a given non-JSON request and 749 other using JSON. One bank might parse a given non-JSON request and
534 deduct money, while the other might reject the transaction with a 750 deduct money, while the other might reject the transaction with a
535 syntax error. While a good protocol will at least recover, that is 751 syntax error. While a good protocol will at least recover, that is
536 extra unnecessary work and the transaction will still not succeed). 752 extra unnecessary work and the transaction will still not succeed).
537 753
538 JSON::DWIW 0.04 754 JSON::DWIW 0.04
539 Very fast. Very natural. Very nice. 755 Very fast. Very natural. Very nice.
540 756
541 Undocumented unicode handling (but the best of the pack. Unicode 757 Undocumented Unicode handling (but the best of the pack. Unicode
542 escapes still don't get parsed properly). 758 escapes still don't get parsed properly).
543 759
544 Very inflexible. 760 Very inflexible.
545 761
546 No roundtripping. 762 No round-tripping.
547 763
548 Does not generate valid JSON texts (key strings are often unquoted, 764 Does not generate valid JSON texts (key strings are often unquoted,
549 empty keys result in nothing being output) 765 empty keys result in nothing being output)
550 766
551 Does not check input for validity. 767 Does not check input for validity.
… …
563 my $yaml = $to_yaml->encode ($ref) . "\n"; 779 my $yaml = $to_yaml->encode ($ref) . "\n";
564 780
565 This will usually generate JSON texts that also parse as valid YAML. 781 This will usually generate JSON texts that also parse as valid YAML.
566 Please note that YAML has hardcoded limits on (simple) object key 782 Please note that YAML has hardcoded limits on (simple) object key
567 lengths that JSON doesn't have, so you should make sure that your hash 783 lengths that JSON doesn't have, so you should make sure that your hash
568 keys are noticably shorter than the 1024 characters YAML allows. 784 keys are noticeably shorter than the 1024 characters YAML allows.
569 785
570 There might be other incompatibilities that I am not aware of. In 786 There might be other incompatibilities that I am not aware of. In
571 general you should not try to generate YAML with a JSON generator or 787 general you should not try to generate YAML with a JSON generator or
572 vice versa, or try to parse JSON with a YAML parser or vice versa: 788 vice versa, or try to parse JSON with a YAML parser or vice versa:
573 chances are high that you will run into severe interoperability 789 chances are high that you will run into severe interoperability
… …
588 It shows the number of encodes/decodes per second (JSON::XS uses the 804 It shows the number of encodes/decodes per second (JSON::XS uses the
589 functional interface, while JSON::XS/2 uses the OO interface with 805 functional interface, while JSON::XS/2 uses the OO interface with
590 pretty-printing and hashkey sorting enabled, JSON::XS/3 enables shrink). 806 pretty-printing and hashkey sorting enabled, JSON::XS/3 enables shrink).
591 Higher is better: 807 Higher is better:
592 808
809 Storable | 15779.925 | 14169.946 |
810 -----------+------------+------------+
593 module | encode | decode | 811 module | encode | decode |
594 -----------|------------|------------| 812 -----------|------------|------------|
595 JSON | 7645.468 | 4208.613 | 813 JSON | 4990.842 | 4088.813 |
596 JSON::DWIW | 40721.398 | 77101.176 | 814 JSON::DWIW | 51653.990 | 71575.154 |
597 JSON::PC | 65948.176 | 78251.940 | 815 JSON::PC | 65948.176 | 74631.744 |
598 JSON::Syck | 22844.793 | 26479.192 | 816 JSON::PP | 8931.652 | 3817.168 |
817 JSON::Syck | 24877.248 | 27776.848 |
599 JSON::XS | 388361.481 | 199728.762 | 818 JSON::XS | 388361.481 | 227951.304 |
600 JSON::XS/2 | 218453.333 | 192399.266 | 819 JSON::XS/2 | 227951.304 | 218453.333 |
601 JSON::XS/3 | 338250.323 | 192399.266 | 820 JSON::XS/3 | 338250.323 | 218453.333 |
602 Storable | 15779.925 | 14169.946 | 821 Storable | 16500.016 | 135300.129 |
603 -----------+------------+------------+ 822 -----------+------------+------------+
604 823
605 That is, JSON::XS is about five times faster than JSON::DWIW on 824 That is, JSON::XS is about five times faster than JSON::DWIW on
606 encoding, about three times faster on decoding, and over fourty times 825 encoding, about three times faster on decoding, and over forty times
607 faster than JSON, even with pretty-printing and key sorting. It also 826 faster than JSON, even with pretty-printing and key sorting. It also
608 compares favourably to Storable for small amounts of data. 827 compares favourably to Storable for small amounts of data.
609 828
610 Using a longer test string (roughly 18KB, generated from Yahoo! Locals 829 Using a longer test string (roughly 18KB, generated from Yahoo! Locals
611 search API (http://nanoref.com/yahooapis/mgPdGg): 830 search API (http://nanoref.com/yahooapis/mgPdGg):
612 831
613 module | encode | decode | 832 module | encode | decode |
614 -----------|------------|------------| 833 -----------|------------|------------|
615 JSON | 254.685 | 37.665 | 834 JSON | 55.260 | 34.971 |
616 JSON::DWIW | 843.343 | 1049.731 | 835 JSON::DWIW | 825.228 | 1082.513 |
617 JSON::PC | 3602.116 | 2307.352 | 836 JSON::PC | 3571.444 | 2394.829 |
837 JSON::PP | 210.987 | 32.574 |
618 JSON::Syck | 505.107 | 787.899 | 838 JSON::Syck | 552.551 | 787.544 |
619 JSON::XS | 5747.196 | 3690.220 | 839 JSON::XS | 5780.463 | 4854.519 |
620 JSON::XS/2 | 3968.121 | 3676.634 | 840 JSON::XS/2 | 3869.998 | 4798.975 |
621 JSON::XS/3 | 6105.246 | 3662.508 | 841 JSON::XS/3 | 5862.880 | 4798.975 |
622 Storable | 4417.337 | 5285.161 | 842 Storable | 4445.002 | 5235.027 |
623 -----------+------------+------------+ 843 -----------+------------+------------+
624 844
625 Again, JSON::XS leads by far (except for Storable which non-surprisingly 845 Again, JSON::XS leads by far (except for Storable which non-surprisingly
626 decodes faster). 846 decodes faster).
627 847
628 On large strings containing lots of high unicode characters, some 848 On large strings containing lots of high Unicode characters, some
629 modules (such as JSON::PC) seem to decode faster than JSON::XS, but the 849 modules (such as JSON::PC) seem to decode faster than JSON::XS, but the
630 result will be broken due to missing (or wrong) unicode handling. Others 850 result will be broken due to missing (or wrong) Unicode handling. Others
631 refuse to decode or encode properly, so it was impossible to prepare a 851 refuse to decode or encode properly, so it was impossible to prepare a
632 fair comparison table for that case. 852 fair comparison table for that case.
633 853
634SECURITY CONSIDERATIONS 854SECURITY CONSIDERATIONS
635 When you are using JSON in a protocol, talking to untrusted potentially 855 When you are using JSON in a protocol, talking to untrusted potentially
… …
639 have any buffer overflows. Obviously, this module should ensure that and 859 have any buffer overflows. Obviously, this module should ensure that and
640 I am trying hard on making that true, but you never know. 860 I am trying hard on making that true, but you never know.
641 861
642 Second, you need to avoid resource-starving attacks. That means you 862 Second, you need to avoid resource-starving attacks. That means you
643 should limit the size of JSON texts you accept, or make sure then when 863 should limit the size of JSON texts you accept, or make sure then when
644 your resources run out, thats just fine (e.g. by using a separate 864 your resources run out, that's just fine (e.g. by using a separate
645 process that can crash safely). The size of a JSON text in octets or 865 process that can crash safely). The size of a JSON text in octets or
646 characters is usually a good indication of the size of the resources 866 characters is usually a good indication of the size of the resources
647 required to decode it into a Perl structure. 867 required to decode it into a Perl structure. While JSON::XS can check
868 the size of the JSON text, it might be too late when you already have it
869 in memory, so you might want to check the size before you accept the
870 string.
648 871
649 Third, JSON::XS recurses using the C stack when decoding objects and 872 Third, JSON::XS recurses using the C stack when decoding objects and
650 arrays. The C stack is a limited resource: for instance, on my amd64 873 arrays. The C stack is a limited resource: for instance, on my amd64
651 machine with 8MB of stack size I can decode around 180k nested arrays 874 machine with 8MB of stack size I can decode around 180k nested arrays
652 but only 14k nested JSON objects (due to perl itself recursing deeply on 875 but only 14k nested JSON objects (due to perl itself recursing deeply on
… …
657 880
658 And last but least, something else could bomb you that I forgot to think 881 And last but least, something else could bomb you that I forgot to think
659 of. In that case, you get to keep the pieces. I am always open for 882 of. In that case, you get to keep the pieces. I am always open for
660 hints, though... 883 hints, though...
661 884
662 If you are using JSON::XS to return packets to consumption by javascript 885 If you are using JSON::XS to return packets to consumption by JavaScript
663 scripts in a browser you should have a look at 886 scripts in a browser you should have a look at
664 <http://jpsykes.com/47/practical-csrf-and-json-security> to see wether 887 <http://jpsykes.com/47/practical-csrf-and-json-security> to see whether
665 you are vulnerable to some common attack vectors (which really are 888 you are vulnerable to some common attack vectors (which really are
666 browser design bugs, but it is still you who will have to deal with it, 889 browser design bugs, but it is still you who will have to deal with it,
667 as major browser developers care only for features, not about doing 890 as major browser developers care only for features, not about doing
668 security right). 891 security right).
892
893THREADS
894 This module is *not* guaranteed to be thread safe and there are no plans
895 to change this until Perl gets thread support (as opposed to the
896 horribly slow so-called "threads" which are simply slow and bloated
897 process simulations - use fork, its *much* faster, cheaper, better).
898
899 (It might actually work, but you have been warned).
669 900
670BUGS 901BUGS
671 While the goal of this module is to be correct, that unfortunately does 902 While the goal of this module is to be correct, that unfortunately does
672 not mean its bug-free, only that I think its design is bug-free. It is 903 not mean its bug-free, only that I think its design is bug-free. It is
673 still relatively early in its development. If you keep reporting bugs 904 still relatively early in its development. If you keep reporting bugs
674 they will be fixed swiftly, though. 905 they will be fixed swiftly, though.
675 906
907 Please refrain from using rt.cpan.org or any other bug reporting
908 service. I put the contact address into my modules for a reason.
909
676AUTHOR 910AUTHOR
677 Marc Lehmann <schmorp@schmorp.de> 911 Marc Lehmann <schmorp@schmorp.de>
678 http://home.schmorp.de/ 912 http://home.schmorp.de/
679 913

Diff Legend

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