1 |
root |
1.1 |
=head1 NAME |
2 |
|
|
|
3 |
|
|
JSON::XS - JSON serialising/deserialising, done correctly and fast |
4 |
|
|
|
5 |
root |
1.62 |
JSON::XS - 正しくて高速な JSON シリアライザ/デシリアライザ |
6 |
|
|
(http://fleur.hio.jp/perldoc/mix/lib/JSON/XS.html) |
7 |
|
|
|
8 |
root |
1.1 |
=head1 SYNOPSIS |
9 |
|
|
|
10 |
|
|
use JSON::XS; |
11 |
|
|
|
12 |
root |
1.22 |
# exported functions, they croak on error |
13 |
|
|
# and expect/generate UTF-8 |
14 |
root |
1.12 |
|
15 |
root |
1.78 |
$utf8_encoded_json_text = encode_json $perl_hash_or_arrayref; |
16 |
|
|
$perl_hash_or_arrayref = decode_json $utf8_encoded_json_text; |
17 |
root |
1.12 |
|
18 |
root |
1.22 |
# OO-interface |
19 |
root |
1.12 |
|
20 |
|
|
$coder = JSON::XS->new->ascii->pretty->allow_nonref; |
21 |
|
|
$pretty_printed_unencoded = $coder->encode ($perl_scalar); |
22 |
|
|
$perl_scalar = $coder->decode ($unicode_json_text); |
23 |
|
|
|
24 |
root |
1.77 |
# Note that JSON version 2.0 and above will automatically use JSON::XS |
25 |
|
|
# if available, at virtually no speed overhead either, so you should |
26 |
|
|
# be able to just: |
27 |
|
|
|
28 |
|
|
use JSON; |
29 |
|
|
|
30 |
|
|
# and do the same things, except that you have a pure-perl fallback now. |
31 |
|
|
|
32 |
root |
1.1 |
=head1 DESCRIPTION |
33 |
|
|
|
34 |
root |
1.2 |
This module converts Perl data structures to JSON and vice versa. Its |
35 |
|
|
primary goal is to be I<correct> and its secondary goal is to be |
36 |
|
|
I<fast>. To reach the latter goal it was written in C. |
37 |
|
|
|
38 |
root |
1.77 |
Beginning with version 2.0 of the JSON module, when both JSON and |
39 |
|
|
JSON::XS are installed, then JSON will fall back on JSON::XS (this can be |
40 |
|
|
overriden) with no overhead due to emulation (by inheritign constructor |
41 |
|
|
and methods). If JSON::XS is not available, it will fall back to the |
42 |
|
|
compatible JSON::PP module as backend, so using JSON instead of JSON::XS |
43 |
|
|
gives you a portable JSON API that can be fast when you need and doesn't |
44 |
|
|
require a C compiler when that is a problem. |
45 |
|
|
|
46 |
root |
1.2 |
As this is the n-th-something JSON module on CPAN, what was the reason |
47 |
|
|
to write yet another JSON module? While it seems there are many JSON |
48 |
|
|
modules, none of them correctly handle all corner cases, and in most cases |
49 |
|
|
their maintainers are unresponsive, gone missing, or not listening to bug |
50 |
|
|
reports for other reasons. |
51 |
|
|
|
52 |
|
|
See COMPARISON, below, for a comparison to some other JSON modules. |
53 |
|
|
|
54 |
root |
1.10 |
See MAPPING, below, on how JSON::XS maps perl values to JSON values and |
55 |
|
|
vice versa. |
56 |
|
|
|
57 |
root |
1.2 |
=head2 FEATURES |
58 |
|
|
|
59 |
root |
1.1 |
=over 4 |
60 |
|
|
|
61 |
root |
1.68 |
=item * correct Unicode handling |
62 |
root |
1.2 |
|
63 |
root |
1.10 |
This module knows how to handle Unicode, and even documents how and when |
64 |
|
|
it does so. |
65 |
root |
1.2 |
|
66 |
|
|
=item * round-trip integrity |
67 |
|
|
|
68 |
|
|
When you serialise a perl data structure using only datatypes supported |
69 |
|
|
by JSON, the deserialised data structure is identical on the Perl level. |
70 |
root |
1.21 |
(e.g. the string "2.0" doesn't suddenly become "2" just because it looks |
71 |
|
|
like a number). |
72 |
root |
1.2 |
|
73 |
|
|
=item * strict checking of JSON correctness |
74 |
|
|
|
75 |
root |
1.16 |
There is no guessing, no generating of illegal JSON texts by default, |
76 |
root |
1.10 |
and only JSON is accepted as input by default (the latter is a security |
77 |
|
|
feature). |
78 |
root |
1.2 |
|
79 |
|
|
=item * fast |
80 |
|
|
|
81 |
root |
1.10 |
Compared to other JSON modules, this module compares favourably in terms |
82 |
|
|
of speed, too. |
83 |
root |
1.2 |
|
84 |
|
|
=item * simple to use |
85 |
|
|
|
86 |
|
|
This module has both a simple functional interface as well as an OO |
87 |
|
|
interface. |
88 |
|
|
|
89 |
|
|
=item * reasonably versatile output formats |
90 |
|
|
|
91 |
root |
1.68 |
You can choose between the most compact guaranteed single-line format |
92 |
root |
1.21 |
possible (nice for simple line-based protocols), a pure-ascii format |
93 |
|
|
(for when your transport is not 8-bit clean, still supports the whole |
94 |
root |
1.68 |
Unicode range), or a pretty-printed format (for when you want to read that |
95 |
root |
1.21 |
stuff). Or you can combine those features in whatever way you like. |
96 |
root |
1.2 |
|
97 |
|
|
=back |
98 |
|
|
|
99 |
root |
1.1 |
=cut |
100 |
|
|
|
101 |
|
|
package JSON::XS; |
102 |
|
|
|
103 |
root |
1.20 |
use strict; |
104 |
|
|
|
105 |
root |
1.78 |
our $VERSION = '2.01'; |
106 |
root |
1.43 |
our @ISA = qw(Exporter); |
107 |
root |
1.1 |
|
108 |
root |
1.78 |
our @EXPORT = qw(encode_json decode_json to_json from_json); |
109 |
|
|
|
110 |
|
|
sub to_json($) { |
111 |
|
|
require Carp; |
112 |
|
|
Carp::croak ("JSON::XS::to_json has been renamed to encode_json, either downgrade to pre-2.0 versions of JSON::XS or rename the call"); |
113 |
|
|
} |
114 |
|
|
|
115 |
|
|
sub from_json($) { |
116 |
|
|
require Carp; |
117 |
|
|
Carp::croak ("JSON::XS::from_json has been renamed to decode_json, either downgrade to pre-2.0 versions of JSON::XS or rename the call"); |
118 |
|
|
} |
119 |
root |
1.1 |
|
120 |
root |
1.43 |
use Exporter; |
121 |
|
|
use XSLoader; |
122 |
root |
1.1 |
|
123 |
root |
1.2 |
=head1 FUNCTIONAL INTERFACE |
124 |
|
|
|
125 |
root |
1.68 |
The following convenience methods are provided by this module. They are |
126 |
root |
1.2 |
exported by default: |
127 |
|
|
|
128 |
|
|
=over 4 |
129 |
|
|
|
130 |
root |
1.78 |
=item $json_text = encode_json $perl_scalar |
131 |
root |
1.2 |
|
132 |
root |
1.63 |
Converts the given Perl data structure to a UTF-8 encoded, binary string |
133 |
|
|
(that is, the string contains octets only). Croaks on error. |
134 |
root |
1.2 |
|
135 |
root |
1.16 |
This function call is functionally identical to: |
136 |
root |
1.2 |
|
137 |
root |
1.16 |
$json_text = JSON::XS->new->utf8->encode ($perl_scalar) |
138 |
|
|
|
139 |
|
|
except being faster. |
140 |
|
|
|
141 |
root |
1.78 |
=item $perl_scalar = decode_json $json_text |
142 |
root |
1.2 |
|
143 |
root |
1.78 |
The opposite of C<encode_json>: expects an UTF-8 (binary) string and tries |
144 |
root |
1.63 |
to parse that as an UTF-8 encoded JSON text, returning the resulting |
145 |
|
|
reference. Croaks on error. |
146 |
root |
1.2 |
|
147 |
root |
1.16 |
This function call is functionally identical to: |
148 |
|
|
|
149 |
|
|
$perl_scalar = JSON::XS->new->utf8->decode ($json_text) |
150 |
|
|
|
151 |
|
|
except being faster. |
152 |
root |
1.2 |
|
153 |
root |
1.43 |
=item $is_boolean = JSON::XS::is_bool $scalar |
154 |
|
|
|
155 |
|
|
Returns true if the passed scalar represents either JSON::XS::true or |
156 |
|
|
JSON::XS::false, two constants that act like C<1> and C<0>, respectively |
157 |
|
|
and are used to represent JSON C<true> and C<false> values in Perl. |
158 |
|
|
|
159 |
|
|
See MAPPING, below, for more information on how JSON values are mapped to |
160 |
|
|
Perl. |
161 |
|
|
|
162 |
root |
1.2 |
=back |
163 |
|
|
|
164 |
root |
1.23 |
|
165 |
root |
1.63 |
=head1 A FEW NOTES ON UNICODE AND PERL |
166 |
|
|
|
167 |
|
|
Since this often leads to confusion, here are a few very clear words on |
168 |
|
|
how Unicode works in Perl, modulo bugs. |
169 |
|
|
|
170 |
|
|
=over 4 |
171 |
|
|
|
172 |
|
|
=item 1. Perl strings can store characters with ordinal values > 255. |
173 |
|
|
|
174 |
root |
1.68 |
This enables you to store Unicode characters as single characters in a |
175 |
root |
1.63 |
Perl string - very natural. |
176 |
|
|
|
177 |
|
|
=item 2. Perl does I<not> associate an encoding with your strings. |
178 |
|
|
|
179 |
|
|
Unless you force it to, e.g. when matching it against a regex, or printing |
180 |
|
|
the scalar to a file, in which case Perl either interprets your string as |
181 |
|
|
locale-encoded text, octets/binary, or as Unicode, depending on various |
182 |
|
|
settings. In no case is an encoding stored together with your data, it is |
183 |
|
|
I<use> that decides encoding, not any magical metadata. |
184 |
|
|
|
185 |
|
|
=item 3. The internal utf-8 flag has no meaning with regards to the |
186 |
|
|
encoding of your string. |
187 |
|
|
|
188 |
|
|
Just ignore that flag unless you debug a Perl bug, a module written in |
189 |
|
|
XS or want to dive into the internals of perl. Otherwise it will only |
190 |
|
|
confuse you, as, despite the name, it says nothing about how your string |
191 |
root |
1.68 |
is encoded. You can have Unicode strings with that flag set, with that |
192 |
root |
1.63 |
flag clear, and you can have binary data with that flag set and that flag |
193 |
|
|
clear. Other possibilities exist, too. |
194 |
|
|
|
195 |
|
|
If you didn't know about that flag, just the better, pretend it doesn't |
196 |
|
|
exist. |
197 |
|
|
|
198 |
|
|
=item 4. A "Unicode String" is simply a string where each character can be |
199 |
|
|
validly interpreted as a Unicode codepoint. |
200 |
|
|
|
201 |
|
|
If you have UTF-8 encoded data, it is no longer a Unicode string, but a |
202 |
|
|
Unicode string encoded in UTF-8, giving you a binary string. |
203 |
|
|
|
204 |
|
|
=item 5. A string containing "high" (> 255) character values is I<not> a UTF-8 string. |
205 |
|
|
|
206 |
root |
1.68 |
It's a fact. Learn to live with it. |
207 |
root |
1.63 |
|
208 |
|
|
=back |
209 |
|
|
|
210 |
|
|
I hope this helps :) |
211 |
|
|
|
212 |
|
|
|
213 |
root |
1.2 |
=head1 OBJECT-ORIENTED INTERFACE |
214 |
|
|
|
215 |
|
|
The object oriented interface lets you configure your own encoding or |
216 |
|
|
decoding style, within the limits of supported formats. |
217 |
|
|
|
218 |
|
|
=over 4 |
219 |
|
|
|
220 |
|
|
=item $json = new JSON::XS |
221 |
|
|
|
222 |
|
|
Creates a new JSON::XS object that can be used to de/encode JSON |
223 |
|
|
strings. All boolean flags described below are by default I<disabled>. |
224 |
root |
1.1 |
|
225 |
root |
1.2 |
The mutators for flags all return the JSON object again and thus calls can |
226 |
|
|
be chained: |
227 |
|
|
|
228 |
root |
1.16 |
my $json = JSON::XS->new->utf8->space_after->encode ({a => [1,2]}) |
229 |
root |
1.3 |
=> {"a": [1, 2]} |
230 |
root |
1.2 |
|
231 |
root |
1.7 |
=item $json = $json->ascii ([$enable]) |
232 |
root |
1.2 |
|
233 |
root |
1.72 |
=item $enabled = $json->get_ascii |
234 |
|
|
|
235 |
root |
1.16 |
If C<$enable> is true (or missing), then the C<encode> method will not |
236 |
|
|
generate characters outside the code range C<0..127> (which is ASCII). Any |
237 |
root |
1.68 |
Unicode characters outside that range will be escaped using either a |
238 |
root |
1.16 |
single \uXXXX (BMP characters) or a double \uHHHH\uLLLLL escape sequence, |
239 |
root |
1.32 |
as per RFC4627. The resulting encoded JSON text can be treated as a native |
240 |
root |
1.68 |
Unicode string, an ascii-encoded, latin1-encoded or UTF-8 encoded string, |
241 |
root |
1.32 |
or any other superset of ASCII. |
242 |
root |
1.2 |
|
243 |
|
|
If C<$enable> is false, then the C<encode> method will not escape Unicode |
244 |
root |
1.33 |
characters unless required by the JSON syntax or other flags. This results |
245 |
|
|
in a faster and more compact format. |
246 |
|
|
|
247 |
|
|
The main use for this flag is to produce JSON texts that can be |
248 |
|
|
transmitted over a 7-bit channel, as the encoded JSON texts will not |
249 |
|
|
contain any 8 bit characters. |
250 |
root |
1.2 |
|
251 |
root |
1.16 |
JSON::XS->new->ascii (1)->encode ([chr 0x10401]) |
252 |
|
|
=> ["\ud801\udc01"] |
253 |
root |
1.3 |
|
254 |
root |
1.33 |
=item $json = $json->latin1 ([$enable]) |
255 |
|
|
|
256 |
root |
1.72 |
=item $enabled = $json->get_latin1 |
257 |
|
|
|
258 |
root |
1.33 |
If C<$enable> is true (or missing), then the C<encode> method will encode |
259 |
|
|
the resulting JSON text as latin1 (or iso-8859-1), escaping any characters |
260 |
|
|
outside the code range C<0..255>. The resulting string can be treated as a |
261 |
root |
1.68 |
latin1-encoded JSON text or a native Unicode string. The C<decode> method |
262 |
root |
1.33 |
will not be affected in any way by this flag, as C<decode> by default |
263 |
root |
1.68 |
expects Unicode, which is a strict superset of latin1. |
264 |
root |
1.33 |
|
265 |
|
|
If C<$enable> is false, then the C<encode> method will not escape Unicode |
266 |
|
|
characters unless required by the JSON syntax or other flags. |
267 |
|
|
|
268 |
|
|
The main use for this flag is efficiently encoding binary data as JSON |
269 |
|
|
text, as most octets will not be escaped, resulting in a smaller encoded |
270 |
|
|
size. The disadvantage is that the resulting JSON text is encoded |
271 |
|
|
in latin1 (and must correctly be treated as such when storing and |
272 |
root |
1.68 |
transferring), a rare encoding for JSON. It is therefore most useful when |
273 |
root |
1.33 |
you want to store data structures known to contain binary data efficiently |
274 |
|
|
in files or databases, not when talking to other JSON encoders/decoders. |
275 |
|
|
|
276 |
|
|
JSON::XS->new->latin1->encode (["\x{89}\x{abc}"] |
277 |
|
|
=> ["\x{89}\\u0abc"] # (perl syntax, U+abc escaped, U+89 not) |
278 |
|
|
|
279 |
root |
1.7 |
=item $json = $json->utf8 ([$enable]) |
280 |
root |
1.2 |
|
281 |
root |
1.72 |
=item $enabled = $json->get_utf8 |
282 |
|
|
|
283 |
root |
1.7 |
If C<$enable> is true (or missing), then the C<encode> method will encode |
284 |
root |
1.16 |
the JSON result into UTF-8, as required by many protocols, while the |
285 |
root |
1.7 |
C<decode> method expects to be handled an UTF-8-encoded string. Please |
286 |
|
|
note that UTF-8-encoded strings do not contain any characters outside the |
287 |
root |
1.16 |
range C<0..255>, they are thus useful for bytewise/binary I/O. In future |
288 |
|
|
versions, enabling this option might enable autodetection of the UTF-16 |
289 |
|
|
and UTF-32 encoding families, as described in RFC4627. |
290 |
root |
1.2 |
|
291 |
|
|
If C<$enable> is false, then the C<encode> method will return the JSON |
292 |
root |
1.68 |
string as a (non-encoded) Unicode string, while C<decode> expects thus a |
293 |
|
|
Unicode string. Any decoding or encoding (e.g. to UTF-8 or UTF-16) needs |
294 |
root |
1.2 |
to be done yourself, e.g. using the Encode module. |
295 |
|
|
|
296 |
root |
1.16 |
Example, output UTF-16BE-encoded JSON: |
297 |
|
|
|
298 |
|
|
use Encode; |
299 |
|
|
$jsontext = encode "UTF-16BE", JSON::XS->new->encode ($object); |
300 |
|
|
|
301 |
|
|
Example, decode UTF-32LE-encoded JSON: |
302 |
|
|
|
303 |
|
|
use Encode; |
304 |
|
|
$object = JSON::XS->new->decode (decode "UTF-32LE", $jsontext); |
305 |
root |
1.12 |
|
306 |
root |
1.7 |
=item $json = $json->pretty ([$enable]) |
307 |
root |
1.2 |
|
308 |
|
|
This enables (or disables) all of the C<indent>, C<space_before> and |
309 |
root |
1.3 |
C<space_after> (and in the future possibly more) flags in one call to |
310 |
root |
1.2 |
generate the most readable (or most compact) form possible. |
311 |
|
|
|
312 |
root |
1.12 |
Example, pretty-print some simple structure: |
313 |
|
|
|
314 |
root |
1.3 |
my $json = JSON::XS->new->pretty(1)->encode ({a => [1,2]}) |
315 |
|
|
=> |
316 |
|
|
{ |
317 |
|
|
"a" : [ |
318 |
|
|
1, |
319 |
|
|
2 |
320 |
|
|
] |
321 |
|
|
} |
322 |
|
|
|
323 |
root |
1.7 |
=item $json = $json->indent ([$enable]) |
324 |
root |
1.2 |
|
325 |
root |
1.72 |
=item $enabled = $json->get_indent |
326 |
|
|
|
327 |
root |
1.7 |
If C<$enable> is true (or missing), then the C<encode> method will use a multiline |
328 |
root |
1.2 |
format as output, putting every array member or object/hash key-value pair |
329 |
root |
1.68 |
into its own line, indenting them properly. |
330 |
root |
1.2 |
|
331 |
|
|
If C<$enable> is false, no newlines or indenting will be produced, and the |
332 |
root |
1.68 |
resulting JSON text is guaranteed not to contain any C<newlines>. |
333 |
root |
1.2 |
|
334 |
root |
1.16 |
This setting has no effect when decoding JSON texts. |
335 |
root |
1.2 |
|
336 |
root |
1.7 |
=item $json = $json->space_before ([$enable]) |
337 |
root |
1.2 |
|
338 |
root |
1.72 |
=item $enabled = $json->get_space_before |
339 |
|
|
|
340 |
root |
1.7 |
If C<$enable> is true (or missing), then the C<encode> method will add an extra |
341 |
root |
1.2 |
optional space before the C<:> separating keys from values in JSON objects. |
342 |
|
|
|
343 |
|
|
If C<$enable> is false, then the C<encode> method will not add any extra |
344 |
|
|
space at those places. |
345 |
|
|
|
346 |
root |
1.16 |
This setting has no effect when decoding JSON texts. You will also |
347 |
|
|
most likely combine this setting with C<space_after>. |
348 |
root |
1.2 |
|
349 |
root |
1.12 |
Example, space_before enabled, space_after and indent disabled: |
350 |
|
|
|
351 |
|
|
{"key" :"value"} |
352 |
|
|
|
353 |
root |
1.7 |
=item $json = $json->space_after ([$enable]) |
354 |
root |
1.2 |
|
355 |
root |
1.72 |
=item $enabled = $json->get_space_after |
356 |
|
|
|
357 |
root |
1.7 |
If C<$enable> is true (or missing), then the C<encode> method will add an extra |
358 |
root |
1.2 |
optional space after the C<:> separating keys from values in JSON objects |
359 |
|
|
and extra whitespace after the C<,> separating key-value pairs and array |
360 |
|
|
members. |
361 |
|
|
|
362 |
|
|
If C<$enable> is false, then the C<encode> method will not add any extra |
363 |
|
|
space at those places. |
364 |
|
|
|
365 |
root |
1.16 |
This setting has no effect when decoding JSON texts. |
366 |
root |
1.2 |
|
367 |
root |
1.12 |
Example, space_before and indent disabled, space_after enabled: |
368 |
|
|
|
369 |
|
|
{"key": "value"} |
370 |
|
|
|
371 |
root |
1.59 |
=item $json = $json->relaxed ([$enable]) |
372 |
|
|
|
373 |
root |
1.72 |
=item $enabled = $json->get_relaxed |
374 |
|
|
|
375 |
root |
1.59 |
If C<$enable> is true (or missing), then C<decode> will accept some |
376 |
|
|
extensions to normal JSON syntax (see below). C<encode> will not be |
377 |
|
|
affected in anyway. I<Be aware that this option makes you accept invalid |
378 |
|
|
JSON texts as if they were valid!>. I suggest only to use this option to |
379 |
|
|
parse application-specific files written by humans (configuration files, |
380 |
|
|
resource files etc.) |
381 |
|
|
|
382 |
|
|
If C<$enable> is false (the default), then C<decode> will only accept |
383 |
|
|
valid JSON texts. |
384 |
|
|
|
385 |
|
|
Currently accepted extensions are: |
386 |
|
|
|
387 |
|
|
=over 4 |
388 |
|
|
|
389 |
|
|
=item * list items can have an end-comma |
390 |
|
|
|
391 |
|
|
JSON I<separates> array elements and key-value pairs with commas. This |
392 |
|
|
can be annoying if you write JSON texts manually and want to be able to |
393 |
|
|
quickly append elements, so this extension accepts comma at the end of |
394 |
|
|
such items not just between them: |
395 |
|
|
|
396 |
|
|
[ |
397 |
|
|
1, |
398 |
|
|
2, <- this comma not normally allowed |
399 |
|
|
] |
400 |
|
|
{ |
401 |
|
|
"k1": "v1", |
402 |
|
|
"k2": "v2", <- this comma not normally allowed |
403 |
|
|
} |
404 |
|
|
|
405 |
root |
1.60 |
=item * shell-style '#'-comments |
406 |
|
|
|
407 |
|
|
Whenever JSON allows whitespace, shell-style comments are additionally |
408 |
|
|
allowed. They are terminated by the first carriage-return or line-feed |
409 |
|
|
character, after which more white-space and comments are allowed. |
410 |
|
|
|
411 |
|
|
[ |
412 |
|
|
1, # this comment not allowed in JSON |
413 |
|
|
# neither this one... |
414 |
|
|
] |
415 |
|
|
|
416 |
root |
1.59 |
=back |
417 |
|
|
|
418 |
root |
1.7 |
=item $json = $json->canonical ([$enable]) |
419 |
root |
1.2 |
|
420 |
root |
1.72 |
=item $enabled = $json->get_canonical |
421 |
|
|
|
422 |
root |
1.7 |
If C<$enable> is true (or missing), then the C<encode> method will output JSON objects |
423 |
root |
1.2 |
by sorting their keys. This is adding a comparatively high overhead. |
424 |
|
|
|
425 |
|
|
If C<$enable> is false, then the C<encode> method will output key-value |
426 |
|
|
pairs in the order Perl stores them (which will likely change between runs |
427 |
|
|
of the same script). |
428 |
|
|
|
429 |
|
|
This option is useful if you want the same data structure to be encoded as |
430 |
root |
1.16 |
the same JSON text (given the same overall settings). If it is disabled, |
431 |
root |
1.68 |
the same hash might be encoded differently even if contains the same data, |
432 |
root |
1.2 |
as key-value pairs have no inherent ordering in Perl. |
433 |
|
|
|
434 |
root |
1.16 |
This setting has no effect when decoding JSON texts. |
435 |
root |
1.2 |
|
436 |
root |
1.7 |
=item $json = $json->allow_nonref ([$enable]) |
437 |
root |
1.3 |
|
438 |
root |
1.72 |
=item $enabled = $json->get_allow_nonref |
439 |
|
|
|
440 |
root |
1.7 |
If C<$enable> is true (or missing), then the C<encode> method can convert a |
441 |
root |
1.3 |
non-reference into its corresponding string, number or null JSON value, |
442 |
|
|
which is an extension to RFC4627. Likewise, C<decode> will accept those JSON |
443 |
|
|
values instead of croaking. |
444 |
|
|
|
445 |
|
|
If C<$enable> is false, then the C<encode> method will croak if it isn't |
446 |
root |
1.16 |
passed an arrayref or hashref, as JSON texts must either be an object |
447 |
root |
1.3 |
or array. Likewise, C<decode> will croak if given something that is not a |
448 |
|
|
JSON object or array. |
449 |
|
|
|
450 |
root |
1.12 |
Example, encode a Perl scalar as JSON value with enabled C<allow_nonref>, |
451 |
|
|
resulting in an invalid JSON text: |
452 |
|
|
|
453 |
|
|
JSON::XS->new->allow_nonref->encode ("Hello, World!") |
454 |
|
|
=> "Hello, World!" |
455 |
|
|
|
456 |
root |
1.44 |
=item $json = $json->allow_blessed ([$enable]) |
457 |
|
|
|
458 |
root |
1.75 |
=item $enabled = $json->get_allow_blessed |
459 |
root |
1.72 |
|
460 |
root |
1.44 |
If C<$enable> is true (or missing), then the C<encode> method will not |
461 |
|
|
barf when it encounters a blessed reference. Instead, the value of the |
462 |
root |
1.68 |
B<convert_blessed> option will decide whether C<null> (C<convert_blessed> |
463 |
root |
1.76 |
disabled or no C<TO_JSON> method found) or a representation of the |
464 |
|
|
object (C<convert_blessed> enabled and C<TO_JSON> method found) is being |
465 |
root |
1.44 |
encoded. Has no effect on C<decode>. |
466 |
|
|
|
467 |
|
|
If C<$enable> is false (the default), then C<encode> will throw an |
468 |
|
|
exception when it encounters a blessed object. |
469 |
|
|
|
470 |
|
|
=item $json = $json->convert_blessed ([$enable]) |
471 |
|
|
|
472 |
root |
1.72 |
=item $enabled = $json->get_convert_blessed |
473 |
|
|
|
474 |
root |
1.44 |
If C<$enable> is true (or missing), then C<encode>, upon encountering a |
475 |
|
|
blessed object, will check for the availability of the C<TO_JSON> method |
476 |
|
|
on the object's class. If found, it will be called in scalar context |
477 |
|
|
and the resulting scalar will be encoded instead of the object. If no |
478 |
|
|
C<TO_JSON> method is found, the value of C<allow_blessed> will decide what |
479 |
|
|
to do. |
480 |
|
|
|
481 |
|
|
The C<TO_JSON> method may safely call die if it wants. If C<TO_JSON> |
482 |
|
|
returns other blessed objects, those will be handled in the same |
483 |
|
|
way. C<TO_JSON> must take care of not causing an endless recursion cycle |
484 |
|
|
(== crash) in this case. The name of C<TO_JSON> was chosen because other |
485 |
root |
1.46 |
methods called by the Perl core (== not by the user of the object) are |
486 |
root |
1.78 |
usually in upper case letters and to avoid collisions with any C<to_json> |
487 |
|
|
function or method. |
488 |
root |
1.44 |
|
489 |
root |
1.45 |
This setting does not yet influence C<decode> in any way, but in the |
490 |
|
|
future, global hooks might get installed that influence C<decode> and are |
491 |
|
|
enabled by this setting. |
492 |
|
|
|
493 |
root |
1.44 |
If C<$enable> is false, then the C<allow_blessed> setting will decide what |
494 |
|
|
to do when a blessed object is found. |
495 |
|
|
|
496 |
root |
1.52 |
=item $json = $json->filter_json_object ([$coderef->($hashref)]) |
497 |
root |
1.51 |
|
498 |
|
|
When C<$coderef> is specified, it will be called from C<decode> each |
499 |
|
|
time it decodes a JSON object. The only argument is a reference to the |
500 |
|
|
newly-created hash. If the code references returns a single scalar (which |
501 |
|
|
need not be a reference), this value (i.e. a copy of that scalar to avoid |
502 |
|
|
aliasing) is inserted into the deserialised data structure. If it returns |
503 |
|
|
an empty list (NOTE: I<not> C<undef>, which is a valid scalar), the |
504 |
|
|
original deserialised hash will be inserted. This setting can slow down |
505 |
|
|
decoding considerably. |
506 |
|
|
|
507 |
root |
1.52 |
When C<$coderef> is omitted or undefined, any existing callback will |
508 |
|
|
be removed and C<decode> will not change the deserialised hash in any |
509 |
|
|
way. |
510 |
root |
1.51 |
|
511 |
|
|
Example, convert all JSON objects into the integer 5: |
512 |
|
|
|
513 |
|
|
my $js = JSON::XS->new->filter_json_object (sub { 5 }); |
514 |
|
|
# returns [5] |
515 |
|
|
$js->decode ('[{}]') |
516 |
root |
1.52 |
# throw an exception because allow_nonref is not enabled |
517 |
|
|
# so a lone 5 is not allowed. |
518 |
root |
1.51 |
$js->decode ('{"a":1, "b":2}'); |
519 |
|
|
|
520 |
root |
1.52 |
=item $json = $json->filter_json_single_key_object ($key [=> $coderef->($value)]) |
521 |
root |
1.51 |
|
522 |
root |
1.52 |
Works remotely similar to C<filter_json_object>, but is only called for |
523 |
|
|
JSON objects having a single key named C<$key>. |
524 |
root |
1.51 |
|
525 |
|
|
This C<$coderef> is called before the one specified via |
526 |
root |
1.52 |
C<filter_json_object>, if any. It gets passed the single value in the JSON |
527 |
|
|
object. If it returns a single value, it will be inserted into the data |
528 |
|
|
structure. If it returns nothing (not even C<undef> but the empty list), |
529 |
|
|
the callback from C<filter_json_object> will be called next, as if no |
530 |
|
|
single-key callback were specified. |
531 |
|
|
|
532 |
|
|
If C<$coderef> is omitted or undefined, the corresponding callback will be |
533 |
|
|
disabled. There can only ever be one callback for a given key. |
534 |
root |
1.51 |
|
535 |
|
|
As this callback gets called less often then the C<filter_json_object> |
536 |
|
|
one, decoding speed will not usually suffer as much. Therefore, single-key |
537 |
|
|
objects make excellent targets to serialise Perl objects into, especially |
538 |
|
|
as single-key JSON objects are as close to the type-tagged value concept |
539 |
root |
1.68 |
as JSON gets (it's basically an ID/VALUE tuple). Of course, JSON does not |
540 |
root |
1.51 |
support this in any way, so you need to make sure your data never looks |
541 |
|
|
like a serialised Perl hash. |
542 |
|
|
|
543 |
|
|
Typical names for the single object key are C<__class_whatever__>, or |
544 |
|
|
C<$__dollars_are_rarely_used__$> or C<}ugly_brace_placement>, or even |
545 |
|
|
things like C<__class_md5sum(classname)__>, to reduce the risk of clashing |
546 |
|
|
with real hashes. |
547 |
|
|
|
548 |
|
|
Example, decode JSON objects of the form C<< { "__widget__" => <id> } >> |
549 |
|
|
into the corresponding C<< $WIDGET{<id>} >> object: |
550 |
|
|
|
551 |
|
|
# return whatever is in $WIDGET{5}: |
552 |
|
|
JSON::XS |
553 |
|
|
->new |
554 |
root |
1.52 |
->filter_json_single_key_object (__widget__ => sub { |
555 |
|
|
$WIDGET{ $_[0] } |
556 |
root |
1.51 |
}) |
557 |
|
|
->decode ('{"__widget__": 5') |
558 |
|
|
|
559 |
|
|
# this can be used with a TO_JSON method in some "widget" class |
560 |
|
|
# for serialisation to json: |
561 |
|
|
sub WidgetBase::TO_JSON { |
562 |
|
|
my ($self) = @_; |
563 |
|
|
|
564 |
|
|
unless ($self->{id}) { |
565 |
|
|
$self->{id} = ..get..some..id..; |
566 |
|
|
$WIDGET{$self->{id}} = $self; |
567 |
|
|
} |
568 |
|
|
|
569 |
|
|
{ __widget__ => $self->{id} } |
570 |
|
|
} |
571 |
|
|
|
572 |
root |
1.7 |
=item $json = $json->shrink ([$enable]) |
573 |
|
|
|
574 |
root |
1.72 |
=item $enabled = $json->get_shrink |
575 |
|
|
|
576 |
root |
1.7 |
Perl usually over-allocates memory a bit when allocating space for |
577 |
root |
1.24 |
strings. This flag optionally resizes strings generated by either |
578 |
root |
1.7 |
C<encode> or C<decode> to their minimum size possible. This can save |
579 |
root |
1.16 |
memory when your JSON texts are either very very long or you have many |
580 |
root |
1.8 |
short strings. It will also try to downgrade any strings to octet-form |
581 |
|
|
if possible: perl stores strings internally either in an encoding called |
582 |
|
|
UTF-X or in octet-form. The latter cannot store everything but uses less |
583 |
root |
1.24 |
space in general (and some buggy Perl or C code might even rely on that |
584 |
|
|
internal representation being used). |
585 |
root |
1.7 |
|
586 |
root |
1.24 |
The actual definition of what shrink does might change in future versions, |
587 |
|
|
but it will always try to save space at the expense of time. |
588 |
|
|
|
589 |
|
|
If C<$enable> is true (or missing), the string returned by C<encode> will |
590 |
|
|
be shrunk-to-fit, while all strings generated by C<decode> will also be |
591 |
|
|
shrunk-to-fit. |
592 |
root |
1.7 |
|
593 |
|
|
If C<$enable> is false, then the normal perl allocation algorithms are used. |
594 |
|
|
If you work with your data, then this is likely to be faster. |
595 |
|
|
|
596 |
|
|
In the future, this setting might control other things, such as converting |
597 |
|
|
strings that look like integers or floats into integers or floats |
598 |
|
|
internally (there is no difference on the Perl level), saving space. |
599 |
|
|
|
600 |
root |
1.23 |
=item $json = $json->max_depth ([$maximum_nesting_depth]) |
601 |
|
|
|
602 |
root |
1.72 |
=item $max_depth = $json->get_max_depth |
603 |
|
|
|
604 |
root |
1.28 |
Sets the maximum nesting level (default C<512>) accepted while encoding |
605 |
root |
1.23 |
or decoding. If the JSON text or Perl data structure has an equal or |
606 |
|
|
higher nesting level then this limit, then the encoder and decoder will |
607 |
|
|
stop and croak at that point. |
608 |
|
|
|
609 |
|
|
Nesting level is defined by number of hash- or arrayrefs that the encoder |
610 |
|
|
needs to traverse to reach a given point or the number of C<{> or C<[> |
611 |
|
|
characters without their matching closing parenthesis crossed to reach a |
612 |
|
|
given character in a string. |
613 |
|
|
|
614 |
|
|
Setting the maximum depth to one disallows any nesting, so that ensures |
615 |
|
|
that the object is only a single hash/object or array. |
616 |
|
|
|
617 |
root |
1.47 |
The argument to C<max_depth> will be rounded up to the next highest power |
618 |
|
|
of two. If no argument is given, the highest possible setting will be |
619 |
|
|
used, which is rarely useful. |
620 |
|
|
|
621 |
|
|
See SECURITY CONSIDERATIONS, below, for more info on why this is useful. |
622 |
|
|
|
623 |
|
|
=item $json = $json->max_size ([$maximum_string_size]) |
624 |
|
|
|
625 |
root |
1.72 |
=item $max_size = $json->get_max_size |
626 |
|
|
|
627 |
root |
1.47 |
Set the maximum length a JSON text may have (in bytes) where decoding is |
628 |
|
|
being attempted. The default is C<0>, meaning no limit. When C<decode> |
629 |
|
|
is called on a string longer then this number of characters it will not |
630 |
|
|
attempt to decode the string but throw an exception. This setting has no |
631 |
|
|
effect on C<encode> (yet). |
632 |
|
|
|
633 |
|
|
The argument to C<max_size> will be rounded up to the next B<highest> |
634 |
|
|
power of two (so may be more than requested). If no argument is given, the |
635 |
|
|
limit check will be deactivated (same as when C<0> is specified). |
636 |
root |
1.23 |
|
637 |
|
|
See SECURITY CONSIDERATIONS, below, for more info on why this is useful. |
638 |
|
|
|
639 |
root |
1.16 |
=item $json_text = $json->encode ($perl_scalar) |
640 |
root |
1.2 |
|
641 |
|
|
Converts the given Perl data structure (a simple scalar or a reference |
642 |
|
|
to a hash or array) to its JSON representation. Simple scalars will be |
643 |
|
|
converted into JSON string or number sequences, while references to arrays |
644 |
|
|
become JSON arrays and references to hashes become JSON objects. Undefined |
645 |
|
|
Perl values (e.g. C<undef>) become JSON C<null> values. Neither C<true> |
646 |
|
|
nor C<false> values will be generated. |
647 |
root |
1.1 |
|
648 |
root |
1.16 |
=item $perl_scalar = $json->decode ($json_text) |
649 |
root |
1.1 |
|
650 |
root |
1.16 |
The opposite of C<encode>: expects a JSON text and tries to parse it, |
651 |
root |
1.2 |
returning the resulting simple scalar or reference. Croaks on error. |
652 |
root |
1.1 |
|
653 |
root |
1.2 |
JSON numbers and strings become simple Perl scalars. JSON arrays become |
654 |
|
|
Perl arrayrefs and JSON objects become Perl hashrefs. C<true> becomes |
655 |
|
|
C<1>, C<false> becomes C<0> and C<null> becomes C<undef>. |
656 |
root |
1.1 |
|
657 |
root |
1.34 |
=item ($perl_scalar, $characters) = $json->decode_prefix ($json_text) |
658 |
|
|
|
659 |
|
|
This works like the C<decode> method, but instead of raising an exception |
660 |
|
|
when there is trailing garbage after the first JSON object, it will |
661 |
|
|
silently stop parsing there and return the number of characters consumed |
662 |
|
|
so far. |
663 |
|
|
|
664 |
|
|
This is useful if your JSON texts are not delimited by an outer protocol |
665 |
|
|
(which is not the brightest thing to do in the first place) and you need |
666 |
|
|
to know where the JSON text ends. |
667 |
|
|
|
668 |
|
|
JSON::XS->new->decode_prefix ("[1] the tail") |
669 |
|
|
=> ([], 3) |
670 |
|
|
|
671 |
root |
1.1 |
=back |
672 |
|
|
|
673 |
root |
1.23 |
|
674 |
root |
1.10 |
=head1 MAPPING |
675 |
|
|
|
676 |
|
|
This section describes how JSON::XS maps Perl values to JSON values and |
677 |
|
|
vice versa. These mappings are designed to "do the right thing" in most |
678 |
|
|
circumstances automatically, preserving round-tripping characteristics |
679 |
|
|
(what you put in comes out as something equivalent). |
680 |
|
|
|
681 |
|
|
For the more enlightened: note that in the following descriptions, |
682 |
root |
1.68 |
lowercase I<perl> refers to the Perl interpreter, while uppercase I<Perl> |
683 |
root |
1.10 |
refers to the abstract Perl language itself. |
684 |
|
|
|
685 |
root |
1.39 |
|
686 |
root |
1.10 |
=head2 JSON -> PERL |
687 |
|
|
|
688 |
|
|
=over 4 |
689 |
|
|
|
690 |
|
|
=item object |
691 |
|
|
|
692 |
|
|
A JSON object becomes a reference to a hash in Perl. No ordering of object |
693 |
root |
1.68 |
keys is preserved (JSON does not preserve object key ordering itself). |
694 |
root |
1.10 |
|
695 |
|
|
=item array |
696 |
|
|
|
697 |
|
|
A JSON array becomes a reference to an array in Perl. |
698 |
|
|
|
699 |
|
|
=item string |
700 |
|
|
|
701 |
|
|
A JSON string becomes a string scalar in Perl - Unicode codepoints in JSON |
702 |
|
|
are represented by the same codepoints in the Perl string, so no manual |
703 |
|
|
decoding is necessary. |
704 |
|
|
|
705 |
|
|
=item number |
706 |
|
|
|
707 |
root |
1.56 |
A JSON number becomes either an integer, numeric (floating point) or |
708 |
|
|
string scalar in perl, depending on its range and any fractional parts. On |
709 |
|
|
the Perl level, there is no difference between those as Perl handles all |
710 |
|
|
the conversion details, but an integer may take slightly less memory and |
711 |
|
|
might represent more values exactly than (floating point) numbers. |
712 |
|
|
|
713 |
|
|
If the number consists of digits only, JSON::XS will try to represent |
714 |
|
|
it as an integer value. If that fails, it will try to represent it as |
715 |
|
|
a numeric (floating point) value if that is possible without loss of |
716 |
|
|
precision. Otherwise it will preserve the number as a string value. |
717 |
|
|
|
718 |
|
|
Numbers containing a fractional or exponential part will always be |
719 |
|
|
represented as numeric (floating point) values, possibly at a loss of |
720 |
|
|
precision. |
721 |
|
|
|
722 |
|
|
This might create round-tripping problems as numbers might become strings, |
723 |
|
|
but as Perl is typeless there is no other way to do it. |
724 |
root |
1.10 |
|
725 |
|
|
=item true, false |
726 |
|
|
|
727 |
root |
1.43 |
These JSON atoms become C<JSON::XS::true> and C<JSON::XS::false>, |
728 |
|
|
respectively. They are overloaded to act almost exactly like the numbers |
729 |
root |
1.68 |
C<1> and C<0>. You can check whether a scalar is a JSON boolean by using |
730 |
root |
1.43 |
the C<JSON::XS::is_bool> function. |
731 |
root |
1.10 |
|
732 |
|
|
=item null |
733 |
|
|
|
734 |
|
|
A JSON null atom becomes C<undef> in Perl. |
735 |
|
|
|
736 |
|
|
=back |
737 |
|
|
|
738 |
root |
1.39 |
|
739 |
root |
1.10 |
=head2 PERL -> JSON |
740 |
|
|
|
741 |
|
|
The mapping from Perl to JSON is slightly more difficult, as Perl is a |
742 |
|
|
truly typeless language, so we can only guess which JSON type is meant by |
743 |
|
|
a Perl value. |
744 |
|
|
|
745 |
|
|
=over 4 |
746 |
|
|
|
747 |
|
|
=item hash references |
748 |
|
|
|
749 |
|
|
Perl hash references become JSON objects. As there is no inherent ordering |
750 |
root |
1.25 |
in hash keys (or JSON objects), they will usually be encoded in a |
751 |
|
|
pseudo-random order that can change between runs of the same program but |
752 |
|
|
stays generally the same within a single run of a program. JSON::XS can |
753 |
|
|
optionally sort the hash keys (determined by the I<canonical> flag), so |
754 |
|
|
the same datastructure will serialise to the same JSON text (given same |
755 |
|
|
settings and version of JSON::XS), but this incurs a runtime overhead |
756 |
|
|
and is only rarely useful, e.g. when you want to compare some JSON text |
757 |
|
|
against another for equality. |
758 |
root |
1.10 |
|
759 |
|
|
=item array references |
760 |
|
|
|
761 |
|
|
Perl array references become JSON arrays. |
762 |
|
|
|
763 |
root |
1.25 |
=item other references |
764 |
|
|
|
765 |
|
|
Other unblessed references are generally not allowed and will cause an |
766 |
|
|
exception to be thrown, except for references to the integers C<0> and |
767 |
|
|
C<1>, which get turned into C<false> and C<true> atoms in JSON. You can |
768 |
|
|
also use C<JSON::XS::false> and C<JSON::XS::true> to improve readability. |
769 |
|
|
|
770 |
root |
1.78 |
encode_json [\0,JSON::XS::true] # yields [false,true] |
771 |
root |
1.25 |
|
772 |
root |
1.43 |
=item JSON::XS::true, JSON::XS::false |
773 |
|
|
|
774 |
|
|
These special values become JSON true and JSON false values, |
775 |
root |
1.61 |
respectively. You can also use C<\1> and C<\0> directly if you want. |
776 |
root |
1.43 |
|
777 |
root |
1.10 |
=item blessed objects |
778 |
|
|
|
779 |
|
|
Blessed objects are not allowed. JSON::XS currently tries to encode their |
780 |
|
|
underlying representation (hash- or arrayref), but this behaviour might |
781 |
|
|
change in future versions. |
782 |
|
|
|
783 |
|
|
=item simple scalars |
784 |
|
|
|
785 |
|
|
Simple Perl scalars (any scalar that is not a reference) are the most |
786 |
|
|
difficult objects to encode: JSON::XS will encode undefined scalars as |
787 |
|
|
JSON null value, scalars that have last been used in a string context |
788 |
|
|
before encoding as JSON strings and anything else as number value: |
789 |
|
|
|
790 |
|
|
# dump as number |
791 |
root |
1.78 |
encode_json [2] # yields [2] |
792 |
|
|
encode_json [-3.0e17] # yields [-3e+17] |
793 |
|
|
my $value = 5; encode_json [$value] # yields [5] |
794 |
root |
1.10 |
|
795 |
|
|
# used as string, so dump as string |
796 |
|
|
print $value; |
797 |
root |
1.78 |
encode_json [$value] # yields ["5"] |
798 |
root |
1.10 |
|
799 |
|
|
# undef becomes null |
800 |
root |
1.78 |
encode_json [undef] # yields [null] |
801 |
root |
1.10 |
|
802 |
root |
1.68 |
You can force the type to be a JSON string by stringifying it: |
803 |
root |
1.10 |
|
804 |
|
|
my $x = 3.1; # some variable containing a number |
805 |
|
|
"$x"; # stringified |
806 |
|
|
$x .= ""; # another, more awkward way to stringify |
807 |
|
|
print $x; # perl does it for you, too, quite often |
808 |
|
|
|
809 |
root |
1.68 |
You can force the type to be a JSON number by numifying it: |
810 |
root |
1.10 |
|
811 |
|
|
my $x = "3"; # some variable containing a string |
812 |
|
|
$x += 0; # numify it, ensuring it will be dumped as a number |
813 |
root |
1.68 |
$x *= 1; # same thing, the choice is yours. |
814 |
root |
1.10 |
|
815 |
root |
1.68 |
You can not currently force the type in other, less obscure, ways. Tell me |
816 |
|
|
if you need this capability. |
817 |
root |
1.10 |
|
818 |
|
|
=back |
819 |
|
|
|
820 |
root |
1.23 |
|
821 |
root |
1.3 |
=head1 COMPARISON |
822 |
|
|
|
823 |
|
|
As already mentioned, this module was created because none of the existing |
824 |
|
|
JSON modules could be made to work correctly. First I will describe the |
825 |
|
|
problems (or pleasures) I encountered with various existing JSON modules, |
826 |
root |
1.4 |
followed by some benchmark values. JSON::XS was designed not to suffer |
827 |
|
|
from any of these problems or limitations. |
828 |
root |
1.3 |
|
829 |
|
|
=over 4 |
830 |
|
|
|
831 |
root |
1.5 |
=item JSON 1.07 |
832 |
root |
1.3 |
|
833 |
|
|
Slow (but very portable, as it is written in pure Perl). |
834 |
|
|
|
835 |
root |
1.68 |
Undocumented/buggy Unicode handling (how JSON handles Unicode values is |
836 |
|
|
undocumented. One can get far by feeding it Unicode strings and doing |
837 |
|
|
en-/decoding oneself, but Unicode escapes are not working properly). |
838 |
root |
1.3 |
|
839 |
root |
1.69 |
No round-tripping (strings get clobbered if they look like numbers, e.g. |
840 |
root |
1.3 |
the string C<2.0> will encode to C<2.0> instead of C<"2.0">, and that will |
841 |
|
|
decode into the number 2. |
842 |
|
|
|
843 |
root |
1.5 |
=item JSON::PC 0.01 |
844 |
root |
1.3 |
|
845 |
|
|
Very fast. |
846 |
|
|
|
847 |
|
|
Undocumented/buggy Unicode handling. |
848 |
|
|
|
849 |
root |
1.69 |
No round-tripping. |
850 |
root |
1.3 |
|
851 |
root |
1.4 |
Has problems handling many Perl values (e.g. regex results and other magic |
852 |
|
|
values will make it croak). |
853 |
root |
1.3 |
|
854 |
|
|
Does not even generate valid JSON (C<{1,2}> gets converted to C<{1:2}> |
855 |
root |
1.16 |
which is not a valid JSON text. |
856 |
root |
1.3 |
|
857 |
|
|
Unmaintained (maintainer unresponsive for many months, bugs are not |
858 |
|
|
getting fixed). |
859 |
|
|
|
860 |
root |
1.5 |
=item JSON::Syck 0.21 |
861 |
root |
1.3 |
|
862 |
|
|
Very buggy (often crashes). |
863 |
|
|
|
864 |
root |
1.4 |
Very inflexible (no human-readable format supported, format pretty much |
865 |
|
|
undocumented. I need at least a format for easy reading by humans and a |
866 |
|
|
single-line compact format for use in a protocol, and preferably a way to |
867 |
root |
1.16 |
generate ASCII-only JSON texts). |
868 |
root |
1.3 |
|
869 |
root |
1.68 |
Completely broken (and confusingly documented) Unicode handling (Unicode |
870 |
root |
1.3 |
escapes are not working properly, you need to set ImplicitUnicode to |
871 |
|
|
I<different> values on en- and decoding to get symmetric behaviour). |
872 |
|
|
|
873 |
root |
1.69 |
No round-tripping (simple cases work, but this depends on whether the scalar |
874 |
root |
1.3 |
value was used in a numeric context or not). |
875 |
|
|
|
876 |
|
|
Dumping hashes may skip hash values depending on iterator state. |
877 |
|
|
|
878 |
|
|
Unmaintained (maintainer unresponsive for many months, bugs are not |
879 |
|
|
getting fixed). |
880 |
|
|
|
881 |
|
|
Does not check input for validity (i.e. will accept non-JSON input and |
882 |
|
|
return "something" instead of raising an exception. This is a security |
883 |
root |
1.68 |
issue: imagine two banks transferring money between each other using |
884 |
root |
1.3 |
JSON. One bank might parse a given non-JSON request and deduct money, |
885 |
|
|
while the other might reject the transaction with a syntax error. While a |
886 |
|
|
good protocol will at least recover, that is extra unnecessary work and |
887 |
|
|
the transaction will still not succeed). |
888 |
|
|
|
889 |
root |
1.5 |
=item JSON::DWIW 0.04 |
890 |
root |
1.3 |
|
891 |
|
|
Very fast. Very natural. Very nice. |
892 |
|
|
|
893 |
root |
1.68 |
Undocumented Unicode handling (but the best of the pack. Unicode escapes |
894 |
root |
1.3 |
still don't get parsed properly). |
895 |
|
|
|
896 |
|
|
Very inflexible. |
897 |
|
|
|
898 |
root |
1.69 |
No round-tripping. |
899 |
root |
1.3 |
|
900 |
root |
1.16 |
Does not generate valid JSON texts (key strings are often unquoted, empty keys |
901 |
root |
1.4 |
result in nothing being output) |
902 |
|
|
|
903 |
root |
1.3 |
Does not check input for validity. |
904 |
|
|
|
905 |
|
|
=back |
906 |
|
|
|
907 |
root |
1.39 |
|
908 |
|
|
=head2 JSON and YAML |
909 |
|
|
|
910 |
root |
1.80 |
You often hear that JSON is a subset of YAML. This is, however, a mass |
911 |
|
|
hysteria and very far from the truth. In general, there is no way to |
912 |
|
|
configure JSON::XS to output a data structure as valid YAML that works for |
913 |
|
|
all cases. |
914 |
root |
1.39 |
|
915 |
root |
1.41 |
If you really must use JSON::XS to generate YAML, you should use this |
916 |
root |
1.39 |
algorithm (subject to change in future versions): |
917 |
|
|
|
918 |
|
|
my $to_yaml = JSON::XS->new->utf8->space_after (1); |
919 |
|
|
my $yaml = $to_yaml->encode ($ref) . "\n"; |
920 |
|
|
|
921 |
|
|
This will usually generate JSON texts that also parse as valid |
922 |
root |
1.41 |
YAML. Please note that YAML has hardcoded limits on (simple) object key |
923 |
root |
1.80 |
lengths that JSON doesn't have and also has different and incompatible |
924 |
|
|
unicode handling, so you should make sure that your hash keys are |
925 |
|
|
noticeably shorter than the 1024 "stream characters" YAML allows and that |
926 |
|
|
you do not have codepoints with values outside the Unicode BMP (basic |
927 |
root |
1.81 |
multilingual page). YAML also does not allow C<\/> sequences in strings |
928 |
|
|
(which JSON::XS does not I<currently> generate). |
929 |
root |
1.39 |
|
930 |
|
|
There might be other incompatibilities that I am not aware of. In general |
931 |
|
|
you should not try to generate YAML with a JSON generator or vice versa, |
932 |
root |
1.41 |
or try to parse JSON with a YAML parser or vice versa: chances are high |
933 |
root |
1.80 |
that you will run into severe interoperability problems when you least |
934 |
|
|
expect it. |
935 |
root |
1.39 |
|
936 |
|
|
|
937 |
root |
1.3 |
=head2 SPEED |
938 |
|
|
|
939 |
root |
1.4 |
It seems that JSON::XS is surprisingly fast, as shown in the following |
940 |
|
|
tables. They have been generated with the help of the C<eg/bench> program |
941 |
|
|
in the JSON::XS distribution, to make it easy to compare on your own |
942 |
|
|
system. |
943 |
|
|
|
944 |
root |
1.37 |
First comes a comparison between various modules using a very short |
945 |
|
|
single-line JSON string: |
946 |
root |
1.18 |
|
947 |
root |
1.37 |
{"method": "handleMessage", "params": ["user1", "we were just talking"], \ |
948 |
root |
1.38 |
"id": null, "array":[1,11,234,-5,1e5,1e7, true, false]} |
949 |
root |
1.18 |
|
950 |
root |
1.39 |
It shows the number of encodes/decodes per second (JSON::XS uses |
951 |
|
|
the functional interface, while JSON::XS/2 uses the OO interface |
952 |
|
|
with pretty-printing and hashkey sorting enabled, JSON::XS/3 enables |
953 |
|
|
shrink). Higher is better: |
954 |
root |
1.4 |
|
955 |
|
|
module | encode | decode | |
956 |
|
|
-----------|------------|------------| |
957 |
root |
1.72 |
JSON 1.x | 4990.842 | 4088.813 | |
958 |
root |
1.48 |
JSON::DWIW | 51653.990 | 71575.154 | |
959 |
|
|
JSON::PC | 65948.176 | 74631.744 | |
960 |
|
|
JSON::PP | 8931.652 | 3817.168 | |
961 |
|
|
JSON::Syck | 24877.248 | 27776.848 | |
962 |
|
|
JSON::XS | 388361.481 | 227951.304 | |
963 |
|
|
JSON::XS/2 | 227951.304 | 218453.333 | |
964 |
|
|
JSON::XS/3 | 338250.323 | 218453.333 | |
965 |
|
|
Storable | 16500.016 | 135300.129 | |
966 |
root |
1.4 |
-----------+------------+------------+ |
967 |
|
|
|
968 |
root |
1.37 |
That is, JSON::XS is about five times faster than JSON::DWIW on encoding, |
969 |
root |
1.68 |
about three times faster on decoding, and over forty times faster |
970 |
root |
1.37 |
than JSON, even with pretty-printing and key sorting. It also compares |
971 |
|
|
favourably to Storable for small amounts of data. |
972 |
root |
1.4 |
|
973 |
root |
1.13 |
Using a longer test string (roughly 18KB, generated from Yahoo! Locals |
974 |
root |
1.4 |
search API (http://nanoref.com/yahooapis/mgPdGg): |
975 |
|
|
|
976 |
|
|
module | encode | decode | |
977 |
|
|
-----------|------------|------------| |
978 |
root |
1.72 |
JSON 1.x | 55.260 | 34.971 | |
979 |
root |
1.48 |
JSON::DWIW | 825.228 | 1082.513 | |
980 |
|
|
JSON::PC | 3571.444 | 2394.829 | |
981 |
|
|
JSON::PP | 210.987 | 32.574 | |
982 |
|
|
JSON::Syck | 552.551 | 787.544 | |
983 |
|
|
JSON::XS | 5780.463 | 4854.519 | |
984 |
|
|
JSON::XS/2 | 3869.998 | 4798.975 | |
985 |
|
|
JSON::XS/3 | 5862.880 | 4798.975 | |
986 |
|
|
Storable | 4445.002 | 5235.027 | |
987 |
root |
1.4 |
-----------+------------+------------+ |
988 |
|
|
|
989 |
root |
1.40 |
Again, JSON::XS leads by far (except for Storable which non-surprisingly |
990 |
|
|
decodes faster). |
991 |
root |
1.4 |
|
992 |
root |
1.68 |
On large strings containing lots of high Unicode characters, some modules |
993 |
root |
1.18 |
(such as JSON::PC) seem to decode faster than JSON::XS, but the result |
994 |
root |
1.68 |
will be broken due to missing (or wrong) Unicode handling. Others refuse |
995 |
root |
1.18 |
to decode or encode properly, so it was impossible to prepare a fair |
996 |
|
|
comparison table for that case. |
997 |
root |
1.13 |
|
998 |
root |
1.11 |
|
999 |
root |
1.23 |
=head1 SECURITY CONSIDERATIONS |
1000 |
|
|
|
1001 |
|
|
When you are using JSON in a protocol, talking to untrusted potentially |
1002 |
|
|
hostile creatures requires relatively few measures. |
1003 |
|
|
|
1004 |
|
|
First of all, your JSON decoder should be secure, that is, should not have |
1005 |
|
|
any buffer overflows. Obviously, this module should ensure that and I am |
1006 |
|
|
trying hard on making that true, but you never know. |
1007 |
|
|
|
1008 |
|
|
Second, you need to avoid resource-starving attacks. That means you should |
1009 |
|
|
limit the size of JSON texts you accept, or make sure then when your |
1010 |
root |
1.68 |
resources run out, that's just fine (e.g. by using a separate process that |
1011 |
root |
1.23 |
can crash safely). The size of a JSON text in octets or characters is |
1012 |
|
|
usually a good indication of the size of the resources required to decode |
1013 |
root |
1.47 |
it into a Perl structure. While JSON::XS can check the size of the JSON |
1014 |
|
|
text, it might be too late when you already have it in memory, so you |
1015 |
|
|
might want to check the size before you accept the string. |
1016 |
root |
1.23 |
|
1017 |
|
|
Third, JSON::XS recurses using the C stack when decoding objects and |
1018 |
|
|
arrays. The C stack is a limited resource: for instance, on my amd64 |
1019 |
root |
1.28 |
machine with 8MB of stack size I can decode around 180k nested arrays but |
1020 |
|
|
only 14k nested JSON objects (due to perl itself recursing deeply on croak |
1021 |
root |
1.79 |
to free the temporary). If that is exceeded, the program crashes. To be |
1022 |
root |
1.28 |
conservative, the default nesting limit is set to 512. If your process |
1023 |
|
|
has a smaller stack, you should adjust this setting accordingly with the |
1024 |
|
|
C<max_depth> method. |
1025 |
root |
1.23 |
|
1026 |
|
|
And last but least, something else could bomb you that I forgot to think |
1027 |
root |
1.30 |
of. In that case, you get to keep the pieces. I am always open for hints, |
1028 |
root |
1.23 |
though... |
1029 |
|
|
|
1030 |
root |
1.42 |
If you are using JSON::XS to return packets to consumption |
1031 |
root |
1.68 |
by JavaScript scripts in a browser you should have a look at |
1032 |
|
|
L<http://jpsykes.com/47/practical-csrf-and-json-security> to see whether |
1033 |
root |
1.42 |
you are vulnerable to some common attack vectors (which really are browser |
1034 |
|
|
design bugs, but it is still you who will have to deal with it, as major |
1035 |
root |
1.79 |
browser developers care only for features, not about getting security |
1036 |
root |
1.42 |
right). |
1037 |
|
|
|
1038 |
root |
1.11 |
|
1039 |
root |
1.64 |
=head1 THREADS |
1040 |
|
|
|
1041 |
root |
1.68 |
This module is I<not> guaranteed to be thread safe and there are no |
1042 |
root |
1.64 |
plans to change this until Perl gets thread support (as opposed to the |
1043 |
|
|
horribly slow so-called "threads" which are simply slow and bloated |
1044 |
|
|
process simulations - use fork, its I<much> faster, cheaper, better). |
1045 |
|
|
|
1046 |
root |
1.68 |
(It might actually work, but you have been warned). |
1047 |
root |
1.64 |
|
1048 |
|
|
|
1049 |
root |
1.4 |
=head1 BUGS |
1050 |
|
|
|
1051 |
|
|
While the goal of this module is to be correct, that unfortunately does |
1052 |
|
|
not mean its bug-free, only that I think its design is bug-free. It is |
1053 |
root |
1.23 |
still relatively early in its development. If you keep reporting bugs they |
1054 |
|
|
will be fixed swiftly, though. |
1055 |
root |
1.4 |
|
1056 |
root |
1.64 |
Please refrain from using rt.cpan.org or any other bug reporting |
1057 |
|
|
service. I put the contact address into my modules for a reason. |
1058 |
|
|
|
1059 |
root |
1.2 |
=cut |
1060 |
|
|
|
1061 |
root |
1.53 |
our $true = do { bless \(my $dummy = 1), "JSON::XS::Boolean" }; |
1062 |
|
|
our $false = do { bless \(my $dummy = 0), "JSON::XS::Boolean" }; |
1063 |
root |
1.43 |
|
1064 |
|
|
sub true() { $true } |
1065 |
|
|
sub false() { $false } |
1066 |
|
|
|
1067 |
|
|
sub is_bool($) { |
1068 |
|
|
UNIVERSAL::isa $_[0], "JSON::XS::Boolean" |
1069 |
root |
1.44 |
# or UNIVERSAL::isa $_[0], "JSON::Literal" |
1070 |
root |
1.43 |
} |
1071 |
|
|
|
1072 |
|
|
XSLoader::load "JSON::XS", $VERSION; |
1073 |
|
|
|
1074 |
|
|
package JSON::XS::Boolean; |
1075 |
|
|
|
1076 |
|
|
use overload |
1077 |
|
|
"0+" => sub { ${$_[0]} }, |
1078 |
|
|
"++" => sub { $_[0] = ${$_[0]} + 1 }, |
1079 |
|
|
"--" => sub { $_[0] = ${$_[0]} - 1 }, |
1080 |
|
|
fallback => 1; |
1081 |
root |
1.25 |
|
1082 |
root |
1.2 |
1; |
1083 |
|
|
|
1084 |
root |
1.1 |
=head1 AUTHOR |
1085 |
|
|
|
1086 |
|
|
Marc Lehmann <schmorp@schmorp.de> |
1087 |
|
|
http://home.schmorp.de/ |
1088 |
|
|
|
1089 |
|
|
=cut |
1090 |
|
|
|