|
|
1 | =head1 NAME |
|
|
2 | |
|
|
3 | JSON::XS - JSON serialising/deserialising, done correctly and fast |
|
|
4 | |
1 | =encoding utf-8 |
5 | =encoding utf-8 |
2 | |
|
|
3 | =head1 NAME |
|
|
4 | |
|
|
5 | JSON::XS - JSON serialising/deserialising, done correctly and fast |
|
|
6 | |
6 | |
7 | JSON::XS - 正しくて高速な JSON シリアライザ/デシリアライザ |
7 | JSON::XS - 正しくて高速な JSON シリアライザ/デシリアライザ |
8 | (http://fleur.hio.jp/perldoc/mix/lib/JSON/XS.html) |
8 | (http://fleur.hio.jp/perldoc/mix/lib/JSON/XS.html) |
9 | |
9 | |
10 | =head1 SYNOPSIS |
10 | =head1 SYNOPSIS |
… | |
… | |
12 | use JSON::XS; |
12 | use JSON::XS; |
13 | |
13 | |
14 | # exported functions, they croak on error |
14 | # exported functions, they croak on error |
15 | # and expect/generate UTF-8 |
15 | # and expect/generate UTF-8 |
16 | |
16 | |
17 | $utf8_encoded_json_text = to_json $perl_hash_or_arrayref; |
17 | $utf8_encoded_json_text = encode_json $perl_hash_or_arrayref; |
18 | $perl_hash_or_arrayref = from_json $utf8_encoded_json_text; |
18 | $perl_hash_or_arrayref = decode_json $utf8_encoded_json_text; |
19 | |
19 | |
20 | # OO-interface |
20 | # OO-interface |
21 | |
21 | |
22 | $coder = JSON::XS->new->ascii->pretty->allow_nonref; |
22 | $coder = JSON::XS->new->ascii->pretty->allow_nonref; |
23 | $pretty_printed_unencoded = $coder->encode ($perl_scalar); |
23 | $pretty_printed_unencoded = $coder->encode ($perl_scalar); |
24 | $perl_scalar = $coder->decode ($unicode_json_text); |
24 | $perl_scalar = $coder->decode ($unicode_json_text); |
25 | |
25 | |
|
|
26 | # Note that JSON version 2.0 and above will automatically use JSON::XS |
|
|
27 | # if available, at virtually no speed overhead either, so you should |
|
|
28 | # be able to just: |
|
|
29 | |
|
|
30 | use JSON; |
|
|
31 | |
|
|
32 | # and do the same things, except that you have a pure-perl fallback now. |
|
|
33 | |
26 | =head1 DESCRIPTION |
34 | =head1 DESCRIPTION |
27 | |
35 | |
28 | This module converts Perl data structures to JSON and vice versa. Its |
36 | This module converts Perl data structures to JSON and vice versa. Its |
29 | primary goal is to be I<correct> and its secondary goal is to be |
37 | primary goal is to be I<correct> and its secondary goal is to be |
30 | I<fast>. To reach the latter goal it was written in C. |
38 | I<fast>. To reach the latter goal it was written in C. |
|
|
39 | |
|
|
40 | Beginning with version 2.0 of the JSON module, when both JSON and |
|
|
41 | JSON::XS are installed, then JSON will fall back on JSON::XS (this can be |
|
|
42 | overridden) with no overhead due to emulation (by inheriting constructor |
|
|
43 | and methods). If JSON::XS is not available, it will fall back to the |
|
|
44 | compatible JSON::PP module as backend, so using JSON instead of JSON::XS |
|
|
45 | gives you a portable JSON API that can be fast when you need and doesn't |
|
|
46 | require a C compiler when that is a problem. |
31 | |
47 | |
32 | As this is the n-th-something JSON module on CPAN, what was the reason |
48 | As this is the n-th-something JSON module on CPAN, what was the reason |
33 | to write yet another JSON module? While it seems there are many JSON |
49 | to write yet another JSON module? While it seems there are many JSON |
34 | modules, none of them correctly handle all corner cases, and in most cases |
50 | modules, none of them correctly handle all corner cases, and in most cases |
35 | their maintainers are unresponsive, gone missing, or not listening to bug |
51 | their maintainers are unresponsive, gone missing, or not listening to bug |
36 | reports for other reasons. |
52 | reports for other reasons. |
37 | |
53 | |
38 | See COMPARISON, below, for a comparison to some other JSON modules. |
|
|
39 | |
|
|
40 | See MAPPING, below, on how JSON::XS maps perl values to JSON values and |
54 | See MAPPING, below, on how JSON::XS maps perl values to JSON values and |
41 | vice versa. |
55 | vice versa. |
42 | |
56 | |
43 | =head2 FEATURES |
57 | =head2 FEATURES |
44 | |
58 | |
45 | =over 4 |
59 | =over 4 |
46 | |
60 | |
47 | =item * correct unicode handling |
61 | =item * correct Unicode handling |
48 | |
62 | |
49 | This module knows how to handle Unicode, and even documents how and when |
63 | This module knows how to handle Unicode, documents how and when it does |
50 | it does so. |
64 | so, and even documents what "correct" means. |
51 | |
65 | |
52 | =item * round-trip integrity |
66 | =item * round-trip integrity |
53 | |
67 | |
54 | When you serialise a perl data structure using only datatypes supported |
68 | When you serialise a perl data structure using only data types supported |
55 | by JSON, the deserialised data structure is identical on the Perl level. |
69 | by JSON, the deserialised data structure is identical on the Perl level. |
56 | (e.g. the string "2.0" doesn't suddenly become "2" just because it looks |
70 | (e.g. the string "2.0" doesn't suddenly become "2" just because it looks |
57 | like a number). |
71 | like a number). There minor I<are> exceptions to this, read the MAPPING |
|
|
72 | section below to learn about those. |
58 | |
73 | |
59 | =item * strict checking of JSON correctness |
74 | =item * strict checking of JSON correctness |
60 | |
75 | |
61 | There is no guessing, no generating of illegal JSON texts by default, |
76 | There is no guessing, no generating of illegal JSON texts by default, |
62 | and only JSON is accepted as input by default (the latter is a security |
77 | and only JSON is accepted as input by default (the latter is a security |
63 | feature). |
78 | feature). |
64 | |
79 | |
65 | =item * fast |
80 | =item * fast |
66 | |
81 | |
67 | Compared to other JSON modules, this module compares favourably in terms |
82 | Compared to other JSON modules and other serialisers such as Storable, |
68 | of speed, too. |
83 | this module usually compares favourably in terms of speed, too. |
69 | |
84 | |
70 | =item * simple to use |
85 | =item * simple to use |
71 | |
86 | |
72 | This module has both a simple functional interface as well as an OO |
87 | This module has both a simple functional interface as well as an object |
73 | interface. |
88 | oriented interface interface. |
74 | |
89 | |
75 | =item * reasonably versatile output formats |
90 | =item * reasonably versatile output formats |
76 | |
91 | |
77 | You can choose between the most compact guarenteed single-line format |
92 | You can choose between the most compact guaranteed-single-line format |
78 | possible (nice for simple line-based protocols), a pure-ascii format |
93 | possible (nice for simple line-based protocols), a pure-ASCII format |
79 | (for when your transport is not 8-bit clean, still supports the whole |
94 | (for when your transport is not 8-bit clean, still supports the whole |
80 | unicode range), or a pretty-printed format (for when you want to read that |
95 | Unicode range), or a pretty-printed format (for when you want to read that |
81 | stuff). Or you can combine those features in whatever way you like. |
96 | stuff). Or you can combine those features in whatever way you like. |
82 | |
97 | |
83 | =back |
98 | =back |
84 | |
99 | |
85 | =cut |
100 | =cut |
86 | |
101 | |
87 | package JSON::XS; |
102 | package JSON::XS; |
88 | |
103 | |
89 | use strict; |
104 | use common::sense; |
90 | |
105 | |
91 | our $VERSION = '1.5'; |
106 | our $VERSION = '2.24'; |
92 | our @ISA = qw(Exporter); |
107 | our @ISA = qw(Exporter); |
93 | |
108 | |
94 | our @EXPORT = qw(to_json from_json); |
109 | our @EXPORT = qw(encode_json decode_json to_json from_json); |
|
|
110 | |
|
|
111 | sub to_json($) { |
|
|
112 | require Carp; |
|
|
113 | 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"); |
|
|
114 | } |
|
|
115 | |
|
|
116 | sub from_json($) { |
|
|
117 | require Carp; |
|
|
118 | 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"); |
|
|
119 | } |
95 | |
120 | |
96 | use Exporter; |
121 | use Exporter; |
97 | use XSLoader; |
122 | use XSLoader; |
98 | |
123 | |
99 | =head1 FUNCTIONAL INTERFACE |
124 | =head1 FUNCTIONAL INTERFACE |
100 | |
125 | |
101 | The following convinience methods are provided by this module. They are |
126 | The following convenience methods are provided by this module. They are |
102 | exported by default: |
127 | exported by default: |
103 | |
128 | |
104 | =over 4 |
129 | =over 4 |
105 | |
130 | |
106 | =item $json_text = to_json $perl_scalar |
131 | =item $json_text = encode_json $perl_scalar |
107 | |
132 | |
108 | Converts the given Perl data structure to a UTF-8 encoded, binary string |
133 | Converts the given Perl data structure to a UTF-8 encoded, binary string |
109 | (that is, the string contains octets only). Croaks on error. |
134 | (that is, the string contains octets only). Croaks on error. |
110 | |
135 | |
111 | This function call is functionally identical to: |
136 | This function call is functionally identical to: |
112 | |
137 | |
113 | $json_text = JSON::XS->new->utf8->encode ($perl_scalar) |
138 | $json_text = JSON::XS->new->utf8->encode ($perl_scalar) |
114 | |
139 | |
115 | except being faster. |
140 | Except being faster. |
116 | |
141 | |
117 | =item $perl_scalar = from_json $json_text |
142 | =item $perl_scalar = decode_json $json_text |
118 | |
143 | |
119 | The opposite of C<to_json>: expects an UTF-8 (binary) string and tries |
144 | The opposite of C<encode_json>: expects an UTF-8 (binary) string and tries |
120 | to parse that as an UTF-8 encoded JSON text, returning the resulting |
145 | to parse that as an UTF-8 encoded JSON text, returning the resulting |
121 | reference. Croaks on error. |
146 | reference. Croaks on error. |
122 | |
147 | |
123 | This function call is functionally identical to: |
148 | This function call is functionally identical to: |
124 | |
149 | |
125 | $perl_scalar = JSON::XS->new->utf8->decode ($json_text) |
150 | $perl_scalar = JSON::XS->new->utf8->decode ($json_text) |
126 | |
151 | |
127 | except being faster. |
152 | Except being faster. |
128 | |
153 | |
129 | =item $is_boolean = JSON::XS::is_bool $scalar |
154 | =item $is_boolean = JSON::XS::is_bool $scalar |
130 | |
155 | |
131 | Returns true if the passed scalar represents either JSON::XS::true or |
156 | Returns true if the passed scalar represents either JSON::XS::true or |
132 | JSON::XS::false, two constants that act like C<1> and C<0>, respectively |
157 | JSON::XS::false, two constants that act like C<1> and C<0>, respectively |
… | |
… | |
145 | |
170 | |
146 | =over 4 |
171 | =over 4 |
147 | |
172 | |
148 | =item 1. Perl strings can store characters with ordinal values > 255. |
173 | =item 1. Perl strings can store characters with ordinal values > 255. |
149 | |
174 | |
150 | This enables you to store unicode characters as single characters in a |
175 | This enables you to store Unicode characters as single characters in a |
151 | Perl string - very natural. |
176 | Perl string - very natural. |
152 | |
177 | |
153 | =item 2. Perl does I<not> associate an encoding with your strings. |
178 | =item 2. Perl does I<not> associate an encoding with your strings. |
154 | |
179 | |
155 | Unless you force it to, e.g. when matching it against a regex, or printing |
180 | ... until you force it to, e.g. when matching it against a regex, or |
156 | the scalar to a file, in which case Perl either interprets your string as |
181 | printing the scalar to a file, in which case Perl either interprets your |
157 | locale-encoded text, octets/binary, or as Unicode, depending on various |
182 | string as locale-encoded text, octets/binary, or as Unicode, depending |
158 | settings. In no case is an encoding stored together with your data, it is |
183 | on various settings. In no case is an encoding stored together with your |
159 | I<use> that decides encoding, not any magical metadata. |
184 | data, it is I<use> that decides encoding, not any magical meta data. |
160 | |
185 | |
161 | =item 3. The internal utf-8 flag has no meaning with regards to the |
186 | =item 3. The internal utf-8 flag has no meaning with regards to the |
162 | encoding of your string. |
187 | encoding of your string. |
163 | |
188 | |
164 | Just ignore that flag unless you debug a Perl bug, a module written in |
189 | Just ignore that flag unless you debug a Perl bug, a module written in |
165 | XS or want to dive into the internals of perl. Otherwise it will only |
190 | XS or want to dive into the internals of perl. Otherwise it will only |
166 | confuse you, as, despite the name, it says nothing about how your string |
191 | confuse you, as, despite the name, it says nothing about how your string |
167 | is encoded. You can have unicode strings with that flag set, with that |
192 | is encoded. You can have Unicode strings with that flag set, with that |
168 | flag clear, and you can have binary data with that flag set and that flag |
193 | flag clear, and you can have binary data with that flag set and that flag |
169 | clear. Other possibilities exist, too. |
194 | clear. Other possibilities exist, too. |
170 | |
195 | |
171 | If you didn't know about that flag, just the better, pretend it doesn't |
196 | If you didn't know about that flag, just the better, pretend it doesn't |
172 | exist. |
197 | exist. |
173 | |
198 | |
174 | =item 4. A "Unicode String" is simply a string where each character can be |
199 | =item 4. A "Unicode String" is simply a string where each character can be |
175 | validly interpreted as a Unicode codepoint. |
200 | validly interpreted as a Unicode code point. |
176 | |
201 | |
177 | If you have UTF-8 encoded data, it is no longer a Unicode string, but a |
202 | If you have UTF-8 encoded data, it is no longer a Unicode string, but a |
178 | Unicode string encoded in UTF-8, giving you a binary string. |
203 | Unicode string encoded in UTF-8, giving you a binary string. |
179 | |
204 | |
180 | =item 5. A string containing "high" (> 255) character values is I<not> a UTF-8 string. |
205 | =item 5. A string containing "high" (> 255) character values is I<not> a UTF-8 string. |
181 | |
206 | |
182 | Its a fact. Learn to live with it. |
207 | It's a fact. Learn to live with it. |
183 | |
208 | |
184 | =back |
209 | =back |
185 | |
210 | |
186 | I hope this helps :) |
211 | I hope this helps :) |
187 | |
212 | |
… | |
… | |
204 | my $json = JSON::XS->new->utf8->space_after->encode ({a => [1,2]}) |
229 | my $json = JSON::XS->new->utf8->space_after->encode ({a => [1,2]}) |
205 | => {"a": [1, 2]} |
230 | => {"a": [1, 2]} |
206 | |
231 | |
207 | =item $json = $json->ascii ([$enable]) |
232 | =item $json = $json->ascii ([$enable]) |
208 | |
233 | |
|
|
234 | =item $enabled = $json->get_ascii |
|
|
235 | |
209 | If C<$enable> is true (or missing), then the C<encode> method will not |
236 | If C<$enable> is true (or missing), then the C<encode> method will not |
210 | generate characters outside the code range C<0..127> (which is ASCII). Any |
237 | generate characters outside the code range C<0..127> (which is ASCII). Any |
211 | unicode characters outside that range will be escaped using either a |
238 | Unicode characters outside that range will be escaped using either a |
212 | single \uXXXX (BMP characters) or a double \uHHHH\uLLLLL escape sequence, |
239 | single \uXXXX (BMP characters) or a double \uHHHH\uLLLLL escape sequence, |
213 | as per RFC4627. The resulting encoded JSON text can be treated as a native |
240 | as per RFC4627. The resulting encoded JSON text can be treated as a native |
214 | unicode string, an ascii-encoded, latin1-encoded or UTF-8 encoded string, |
241 | Unicode string, an ascii-encoded, latin1-encoded or UTF-8 encoded string, |
215 | or any other superset of ASCII. |
242 | or any other superset of ASCII. |
216 | |
243 | |
217 | If C<$enable> is false, then the C<encode> method will not escape Unicode |
244 | If C<$enable> is false, then the C<encode> method will not escape Unicode |
218 | characters unless required by the JSON syntax or other flags. This results |
245 | characters unless required by the JSON syntax or other flags. This results |
219 | in a faster and more compact format. |
246 | in a faster and more compact format. |
220 | |
247 | |
|
|
248 | See also the section I<ENCODING/CODESET FLAG NOTES> later in this |
|
|
249 | document. |
|
|
250 | |
221 | The main use for this flag is to produce JSON texts that can be |
251 | The main use for this flag is to produce JSON texts that can be |
222 | transmitted over a 7-bit channel, as the encoded JSON texts will not |
252 | transmitted over a 7-bit channel, as the encoded JSON texts will not |
223 | contain any 8 bit characters. |
253 | contain any 8 bit characters. |
224 | |
254 | |
225 | JSON::XS->new->ascii (1)->encode ([chr 0x10401]) |
255 | JSON::XS->new->ascii (1)->encode ([chr 0x10401]) |
226 | => ["\ud801\udc01"] |
256 | => ["\ud801\udc01"] |
227 | |
257 | |
228 | =item $json = $json->latin1 ([$enable]) |
258 | =item $json = $json->latin1 ([$enable]) |
229 | |
259 | |
|
|
260 | =item $enabled = $json->get_latin1 |
|
|
261 | |
230 | If C<$enable> is true (or missing), then the C<encode> method will encode |
262 | If C<$enable> is true (or missing), then the C<encode> method will encode |
231 | the resulting JSON text as latin1 (or iso-8859-1), escaping any characters |
263 | the resulting JSON text as latin1 (or iso-8859-1), escaping any characters |
232 | outside the code range C<0..255>. The resulting string can be treated as a |
264 | outside the code range C<0..255>. The resulting string can be treated as a |
233 | latin1-encoded JSON text or a native unicode string. The C<decode> method |
265 | latin1-encoded JSON text or a native Unicode string. The C<decode> method |
234 | will not be affected in any way by this flag, as C<decode> by default |
266 | will not be affected in any way by this flag, as C<decode> by default |
235 | expects unicode, which is a strict superset of latin1. |
267 | expects Unicode, which is a strict superset of latin1. |
236 | |
268 | |
237 | If C<$enable> is false, then the C<encode> method will not escape Unicode |
269 | If C<$enable> is false, then the C<encode> method will not escape Unicode |
238 | characters unless required by the JSON syntax or other flags. |
270 | characters unless required by the JSON syntax or other flags. |
|
|
271 | |
|
|
272 | See also the section I<ENCODING/CODESET FLAG NOTES> later in this |
|
|
273 | document. |
239 | |
274 | |
240 | The main use for this flag is efficiently encoding binary data as JSON |
275 | The main use for this flag is efficiently encoding binary data as JSON |
241 | text, as most octets will not be escaped, resulting in a smaller encoded |
276 | text, as most octets will not be escaped, resulting in a smaller encoded |
242 | size. The disadvantage is that the resulting JSON text is encoded |
277 | size. The disadvantage is that the resulting JSON text is encoded |
243 | in latin1 (and must correctly be treated as such when storing and |
278 | in latin1 (and must correctly be treated as such when storing and |
244 | transfering), a rare encoding for JSON. It is therefore most useful when |
279 | transferring), a rare encoding for JSON. It is therefore most useful when |
245 | you want to store data structures known to contain binary data efficiently |
280 | you want to store data structures known to contain binary data efficiently |
246 | in files or databases, not when talking to other JSON encoders/decoders. |
281 | in files or databases, not when talking to other JSON encoders/decoders. |
247 | |
282 | |
248 | JSON::XS->new->latin1->encode (["\x{89}\x{abc}"] |
283 | JSON::XS->new->latin1->encode (["\x{89}\x{abc}"] |
249 | => ["\x{89}\\u0abc"] # (perl syntax, U+abc escaped, U+89 not) |
284 | => ["\x{89}\\u0abc"] # (perl syntax, U+abc escaped, U+89 not) |
250 | |
285 | |
251 | =item $json = $json->utf8 ([$enable]) |
286 | =item $json = $json->utf8 ([$enable]) |
|
|
287 | |
|
|
288 | =item $enabled = $json->get_utf8 |
252 | |
289 | |
253 | If C<$enable> is true (or missing), then the C<encode> method will encode |
290 | If C<$enable> is true (or missing), then the C<encode> method will encode |
254 | the JSON result into UTF-8, as required by many protocols, while the |
291 | the JSON result into UTF-8, as required by many protocols, while the |
255 | C<decode> method expects to be handled an UTF-8-encoded string. Please |
292 | C<decode> method expects to be handled an UTF-8-encoded string. Please |
256 | note that UTF-8-encoded strings do not contain any characters outside the |
293 | note that UTF-8-encoded strings do not contain any characters outside the |
257 | range C<0..255>, they are thus useful for bytewise/binary I/O. In future |
294 | range C<0..255>, they are thus useful for bytewise/binary I/O. In future |
258 | versions, enabling this option might enable autodetection of the UTF-16 |
295 | versions, enabling this option might enable autodetection of the UTF-16 |
259 | and UTF-32 encoding families, as described in RFC4627. |
296 | and UTF-32 encoding families, as described in RFC4627. |
260 | |
297 | |
261 | If C<$enable> is false, then the C<encode> method will return the JSON |
298 | If C<$enable> is false, then the C<encode> method will return the JSON |
262 | string as a (non-encoded) unicode string, while C<decode> expects thus a |
299 | string as a (non-encoded) Unicode string, while C<decode> expects thus a |
263 | unicode string. Any decoding or encoding (e.g. to UTF-8 or UTF-16) needs |
300 | Unicode string. Any decoding or encoding (e.g. to UTF-8 or UTF-16) needs |
264 | to be done yourself, e.g. using the Encode module. |
301 | to be done yourself, e.g. using the Encode module. |
|
|
302 | |
|
|
303 | See also the section I<ENCODING/CODESET FLAG NOTES> later in this |
|
|
304 | document. |
265 | |
305 | |
266 | Example, output UTF-16BE-encoded JSON: |
306 | Example, output UTF-16BE-encoded JSON: |
267 | |
307 | |
268 | use Encode; |
308 | use Encode; |
269 | $jsontext = encode "UTF-16BE", JSON::XS->new->encode ($object); |
309 | $jsontext = encode "UTF-16BE", JSON::XS->new->encode ($object); |
… | |
… | |
290 | ] |
330 | ] |
291 | } |
331 | } |
292 | |
332 | |
293 | =item $json = $json->indent ([$enable]) |
333 | =item $json = $json->indent ([$enable]) |
294 | |
334 | |
|
|
335 | =item $enabled = $json->get_indent |
|
|
336 | |
295 | If C<$enable> is true (or missing), then the C<encode> method will use a multiline |
337 | If C<$enable> is true (or missing), then the C<encode> method will use a multiline |
296 | format as output, putting every array member or object/hash key-value pair |
338 | format as output, putting every array member or object/hash key-value pair |
297 | into its own line, identing them properly. |
339 | into its own line, indenting them properly. |
298 | |
340 | |
299 | If C<$enable> is false, no newlines or indenting will be produced, and the |
341 | If C<$enable> is false, no newlines or indenting will be produced, and the |
300 | resulting JSON text is guarenteed not to contain any C<newlines>. |
342 | resulting JSON text is guaranteed not to contain any C<newlines>. |
301 | |
343 | |
302 | This setting has no effect when decoding JSON texts. |
344 | This setting has no effect when decoding JSON texts. |
303 | |
345 | |
304 | =item $json = $json->space_before ([$enable]) |
346 | =item $json = $json->space_before ([$enable]) |
|
|
347 | |
|
|
348 | =item $enabled = $json->get_space_before |
305 | |
349 | |
306 | If C<$enable> is true (or missing), then the C<encode> method will add an extra |
350 | If C<$enable> is true (or missing), then the C<encode> method will add an extra |
307 | optional space before the C<:> separating keys from values in JSON objects. |
351 | optional space before the C<:> separating keys from values in JSON objects. |
308 | |
352 | |
309 | If C<$enable> is false, then the C<encode> method will not add any extra |
353 | If C<$enable> is false, then the C<encode> method will not add any extra |
… | |
… | |
315 | Example, space_before enabled, space_after and indent disabled: |
359 | Example, space_before enabled, space_after and indent disabled: |
316 | |
360 | |
317 | {"key" :"value"} |
361 | {"key" :"value"} |
318 | |
362 | |
319 | =item $json = $json->space_after ([$enable]) |
363 | =item $json = $json->space_after ([$enable]) |
|
|
364 | |
|
|
365 | =item $enabled = $json->get_space_after |
320 | |
366 | |
321 | If C<$enable> is true (or missing), then the C<encode> method will add an extra |
367 | If C<$enable> is true (or missing), then the C<encode> method will add an extra |
322 | optional space after the C<:> separating keys from values in JSON objects |
368 | optional space after the C<:> separating keys from values in JSON objects |
323 | and extra whitespace after the C<,> separating key-value pairs and array |
369 | and extra whitespace after the C<,> separating key-value pairs and array |
324 | members. |
370 | members. |
… | |
… | |
331 | Example, space_before and indent disabled, space_after enabled: |
377 | Example, space_before and indent disabled, space_after enabled: |
332 | |
378 | |
333 | {"key": "value"} |
379 | {"key": "value"} |
334 | |
380 | |
335 | =item $json = $json->relaxed ([$enable]) |
381 | =item $json = $json->relaxed ([$enable]) |
|
|
382 | |
|
|
383 | =item $enabled = $json->get_relaxed |
336 | |
384 | |
337 | If C<$enable> is true (or missing), then C<decode> will accept some |
385 | If C<$enable> is true (or missing), then C<decode> will accept some |
338 | extensions to normal JSON syntax (see below). C<encode> will not be |
386 | extensions to normal JSON syntax (see below). C<encode> will not be |
339 | affected in anyway. I<Be aware that this option makes you accept invalid |
387 | affected in anyway. I<Be aware that this option makes you accept invalid |
340 | JSON texts as if they were valid!>. I suggest only to use this option to |
388 | JSON texts as if they were valid!>. I suggest only to use this option to |
… | |
… | |
377 | |
425 | |
378 | =back |
426 | =back |
379 | |
427 | |
380 | =item $json = $json->canonical ([$enable]) |
428 | =item $json = $json->canonical ([$enable]) |
381 | |
429 | |
|
|
430 | =item $enabled = $json->get_canonical |
|
|
431 | |
382 | If C<$enable> is true (or missing), then the C<encode> method will output JSON objects |
432 | If C<$enable> is true (or missing), then the C<encode> method will output JSON objects |
383 | by sorting their keys. This is adding a comparatively high overhead. |
433 | by sorting their keys. This is adding a comparatively high overhead. |
384 | |
434 | |
385 | If C<$enable> is false, then the C<encode> method will output key-value |
435 | If C<$enable> is false, then the C<encode> method will output key-value |
386 | pairs in the order Perl stores them (which will likely change between runs |
436 | pairs in the order Perl stores them (which will likely change between runs |
387 | of the same script). |
437 | of the same script). |
388 | |
438 | |
389 | This option is useful if you want the same data structure to be encoded as |
439 | This option is useful if you want the same data structure to be encoded as |
390 | the same JSON text (given the same overall settings). If it is disabled, |
440 | the same JSON text (given the same overall settings). If it is disabled, |
391 | the same hash migh be encoded differently even if contains the same data, |
441 | the same hash might be encoded differently even if contains the same data, |
392 | as key-value pairs have no inherent ordering in Perl. |
442 | as key-value pairs have no inherent ordering in Perl. |
393 | |
443 | |
394 | This setting has no effect when decoding JSON texts. |
444 | This setting has no effect when decoding JSON texts. |
395 | |
445 | |
396 | =item $json = $json->allow_nonref ([$enable]) |
446 | =item $json = $json->allow_nonref ([$enable]) |
|
|
447 | |
|
|
448 | =item $enabled = $json->get_allow_nonref |
397 | |
449 | |
398 | If C<$enable> is true (or missing), then the C<encode> method can convert a |
450 | If C<$enable> is true (or missing), then the C<encode> method can convert a |
399 | non-reference into its corresponding string, number or null JSON value, |
451 | non-reference into its corresponding string, number or null JSON value, |
400 | which is an extension to RFC4627. Likewise, C<decode> will accept those JSON |
452 | which is an extension to RFC4627. Likewise, C<decode> will accept those JSON |
401 | values instead of croaking. |
453 | values instead of croaking. |
… | |
… | |
409 | resulting in an invalid JSON text: |
461 | resulting in an invalid JSON text: |
410 | |
462 | |
411 | JSON::XS->new->allow_nonref->encode ("Hello, World!") |
463 | JSON::XS->new->allow_nonref->encode ("Hello, World!") |
412 | => "Hello, World!" |
464 | => "Hello, World!" |
413 | |
465 | |
|
|
466 | =item $json = $json->allow_unknown ([$enable]) |
|
|
467 | |
|
|
468 | =item $enabled = $json->get_allow_unknown |
|
|
469 | |
|
|
470 | If C<$enable> is true (or missing), then C<encode> will I<not> throw an |
|
|
471 | exception when it encounters values it cannot represent in JSON (for |
|
|
472 | example, filehandles) but instead will encode a JSON C<null> value. Note |
|
|
473 | that blessed objects are not included here and are handled separately by |
|
|
474 | c<allow_nonref>. |
|
|
475 | |
|
|
476 | If C<$enable> is false (the default), then C<encode> will throw an |
|
|
477 | exception when it encounters anything it cannot encode as JSON. |
|
|
478 | |
|
|
479 | This option does not affect C<decode> in any way, and it is recommended to |
|
|
480 | leave it off unless you know your communications partner. |
|
|
481 | |
414 | =item $json = $json->allow_blessed ([$enable]) |
482 | =item $json = $json->allow_blessed ([$enable]) |
|
|
483 | |
|
|
484 | =item $enabled = $json->get_allow_blessed |
415 | |
485 | |
416 | If C<$enable> is true (or missing), then the C<encode> method will not |
486 | If C<$enable> is true (or missing), then the C<encode> method will not |
417 | barf when it encounters a blessed reference. Instead, the value of the |
487 | barf when it encounters a blessed reference. Instead, the value of the |
418 | B<convert_blessed> option will decide wether C<null> (C<convert_blessed> |
488 | B<convert_blessed> option will decide whether C<null> (C<convert_blessed> |
419 | disabled or no C<to_json> method found) or a representation of the |
489 | disabled or no C<TO_JSON> method found) or a representation of the |
420 | object (C<convert_blessed> enabled and C<to_json> method found) is being |
490 | object (C<convert_blessed> enabled and C<TO_JSON> method found) is being |
421 | encoded. Has no effect on C<decode>. |
491 | encoded. Has no effect on C<decode>. |
422 | |
492 | |
423 | If C<$enable> is false (the default), then C<encode> will throw an |
493 | If C<$enable> is false (the default), then C<encode> will throw an |
424 | exception when it encounters a blessed object. |
494 | exception when it encounters a blessed object. |
425 | |
495 | |
426 | =item $json = $json->convert_blessed ([$enable]) |
496 | =item $json = $json->convert_blessed ([$enable]) |
|
|
497 | |
|
|
498 | =item $enabled = $json->get_convert_blessed |
427 | |
499 | |
428 | If C<$enable> is true (or missing), then C<encode>, upon encountering a |
500 | If C<$enable> is true (or missing), then C<encode>, upon encountering a |
429 | blessed object, will check for the availability of the C<TO_JSON> method |
501 | blessed object, will check for the availability of the C<TO_JSON> method |
430 | on the object's class. If found, it will be called in scalar context |
502 | on the object's class. If found, it will be called in scalar context |
431 | and the resulting scalar will be encoded instead of the object. If no |
503 | and the resulting scalar will be encoded instead of the object. If no |
… | |
… | |
435 | The C<TO_JSON> method may safely call die if it wants. If C<TO_JSON> |
507 | The C<TO_JSON> method may safely call die if it wants. If C<TO_JSON> |
436 | returns other blessed objects, those will be handled in the same |
508 | returns other blessed objects, those will be handled in the same |
437 | way. C<TO_JSON> must take care of not causing an endless recursion cycle |
509 | way. C<TO_JSON> must take care of not causing an endless recursion cycle |
438 | (== crash) in this case. The name of C<TO_JSON> was chosen because other |
510 | (== crash) in this case. The name of C<TO_JSON> was chosen because other |
439 | methods called by the Perl core (== not by the user of the object) are |
511 | methods called by the Perl core (== not by the user of the object) are |
440 | usually in upper case letters and to avoid collisions with the C<to_json> |
512 | usually in upper case letters and to avoid collisions with any C<to_json> |
441 | function. |
513 | function or method. |
442 | |
514 | |
443 | This setting does not yet influence C<decode> in any way, but in the |
515 | This setting does not yet influence C<decode> in any way, but in the |
444 | future, global hooks might get installed that influence C<decode> and are |
516 | future, global hooks might get installed that influence C<decode> and are |
445 | enabled by this setting. |
517 | enabled by this setting. |
446 | |
518 | |
… | |
… | |
488 | |
560 | |
489 | As this callback gets called less often then the C<filter_json_object> |
561 | As this callback gets called less often then the C<filter_json_object> |
490 | one, decoding speed will not usually suffer as much. Therefore, single-key |
562 | one, decoding speed will not usually suffer as much. Therefore, single-key |
491 | objects make excellent targets to serialise Perl objects into, especially |
563 | objects make excellent targets to serialise Perl objects into, especially |
492 | as single-key JSON objects are as close to the type-tagged value concept |
564 | as single-key JSON objects are as close to the type-tagged value concept |
493 | as JSON gets (its basically an ID/VALUE tuple). Of course, JSON does not |
565 | as JSON gets (it's basically an ID/VALUE tuple). Of course, JSON does not |
494 | support this in any way, so you need to make sure your data never looks |
566 | support this in any way, so you need to make sure your data never looks |
495 | like a serialised Perl hash. |
567 | like a serialised Perl hash. |
496 | |
568 | |
497 | Typical names for the single object key are C<__class_whatever__>, or |
569 | Typical names for the single object key are C<__class_whatever__>, or |
498 | C<$__dollars_are_rarely_used__$> or C<}ugly_brace_placement>, or even |
570 | C<$__dollars_are_rarely_used__$> or C<}ugly_brace_placement>, or even |
… | |
… | |
522 | |
594 | |
523 | { __widget__ => $self->{id} } |
595 | { __widget__ => $self->{id} } |
524 | } |
596 | } |
525 | |
597 | |
526 | =item $json = $json->shrink ([$enable]) |
598 | =item $json = $json->shrink ([$enable]) |
|
|
599 | |
|
|
600 | =item $enabled = $json->get_shrink |
527 | |
601 | |
528 | Perl usually over-allocates memory a bit when allocating space for |
602 | Perl usually over-allocates memory a bit when allocating space for |
529 | strings. This flag optionally resizes strings generated by either |
603 | strings. This flag optionally resizes strings generated by either |
530 | C<encode> or C<decode> to their minimum size possible. This can save |
604 | C<encode> or C<decode> to their minimum size possible. This can save |
531 | memory when your JSON texts are either very very long or you have many |
605 | memory when your JSON texts are either very very long or you have many |
… | |
… | |
549 | strings that look like integers or floats into integers or floats |
623 | strings that look like integers or floats into integers or floats |
550 | internally (there is no difference on the Perl level), saving space. |
624 | internally (there is no difference on the Perl level), saving space. |
551 | |
625 | |
552 | =item $json = $json->max_depth ([$maximum_nesting_depth]) |
626 | =item $json = $json->max_depth ([$maximum_nesting_depth]) |
553 | |
627 | |
|
|
628 | =item $max_depth = $json->get_max_depth |
|
|
629 | |
554 | Sets the maximum nesting level (default C<512>) accepted while encoding |
630 | Sets the maximum nesting level (default C<512>) accepted while encoding |
555 | or decoding. If the JSON text or Perl data structure has an equal or |
631 | or decoding. If a higher nesting level is detected in JSON text or a Perl |
556 | higher nesting level then this limit, then the encoder and decoder will |
632 | data structure, then the encoder and decoder will stop and croak at that |
557 | stop and croak at that point. |
633 | point. |
558 | |
634 | |
559 | Nesting level is defined by number of hash- or arrayrefs that the encoder |
635 | Nesting level is defined by number of hash- or arrayrefs that the encoder |
560 | needs to traverse to reach a given point or the number of C<{> or C<[> |
636 | needs to traverse to reach a given point or the number of C<{> or C<[> |
561 | characters without their matching closing parenthesis crossed to reach a |
637 | characters without their matching closing parenthesis crossed to reach a |
562 | given character in a string. |
638 | given character in a string. |
563 | |
639 | |
564 | Setting the maximum depth to one disallows any nesting, so that ensures |
640 | Setting the maximum depth to one disallows any nesting, so that ensures |
565 | that the object is only a single hash/object or array. |
641 | that the object is only a single hash/object or array. |
566 | |
642 | |
567 | The argument to C<max_depth> will be rounded up to the next highest power |
|
|
568 | of two. If no argument is given, the highest possible setting will be |
643 | If no argument is given, the highest possible setting will be used, which |
569 | used, which is rarely useful. |
644 | is rarely useful. |
|
|
645 | |
|
|
646 | Note that nesting is implemented by recursion in C. The default value has |
|
|
647 | been chosen to be as large as typical operating systems allow without |
|
|
648 | crashing. |
570 | |
649 | |
571 | See SECURITY CONSIDERATIONS, below, for more info on why this is useful. |
650 | See SECURITY CONSIDERATIONS, below, for more info on why this is useful. |
572 | |
651 | |
573 | =item $json = $json->max_size ([$maximum_string_size]) |
652 | =item $json = $json->max_size ([$maximum_string_size]) |
|
|
653 | |
|
|
654 | =item $max_size = $json->get_max_size |
574 | |
655 | |
575 | Set the maximum length a JSON text may have (in bytes) where decoding is |
656 | Set the maximum length a JSON text may have (in bytes) where decoding is |
576 | being attempted. The default is C<0>, meaning no limit. When C<decode> |
657 | being attempted. The default is C<0>, meaning no limit. When C<decode> |
577 | is called on a string longer then this number of characters it will not |
658 | is called on a string that is longer then this many bytes, it will not |
578 | attempt to decode the string but throw an exception. This setting has no |
659 | attempt to decode the string but throw an exception. This setting has no |
579 | effect on C<encode> (yet). |
660 | effect on C<encode> (yet). |
580 | |
661 | |
581 | The argument to C<max_size> will be rounded up to the next B<highest> |
662 | If no argument is given, the limit check will be deactivated (same as when |
582 | power of two (so may be more than requested). If no argument is given, the |
663 | C<0> is specified). |
583 | limit check will be deactivated (same as when C<0> is specified). |
|
|
584 | |
664 | |
585 | See SECURITY CONSIDERATIONS, below, for more info on why this is useful. |
665 | See SECURITY CONSIDERATIONS, below, for more info on why this is useful. |
586 | |
666 | |
587 | =item $json_text = $json->encode ($perl_scalar) |
667 | =item $json_text = $json->encode ($perl_scalar) |
588 | |
668 | |
… | |
… | |
617 | => ([], 3) |
697 | => ([], 3) |
618 | |
698 | |
619 | =back |
699 | =back |
620 | |
700 | |
621 | |
701 | |
|
|
702 | =head1 INCREMENTAL PARSING |
|
|
703 | |
|
|
704 | In some cases, there is the need for incremental parsing of JSON |
|
|
705 | texts. While this module always has to keep both JSON text and resulting |
|
|
706 | Perl data structure in memory at one time, it does allow you to parse a |
|
|
707 | JSON stream incrementally. It does so by accumulating text until it has |
|
|
708 | a full JSON object, which it then can decode. This process is similar to |
|
|
709 | using C<decode_prefix> to see if a full JSON object is available, but |
|
|
710 | is much more efficient (and can be implemented with a minimum of method |
|
|
711 | calls). |
|
|
712 | |
|
|
713 | JSON::XS will only attempt to parse the JSON text once it is sure it |
|
|
714 | has enough text to get a decisive result, using a very simple but |
|
|
715 | truly incremental parser. This means that it sometimes won't stop as |
|
|
716 | early as the full parser, for example, it doesn't detect parenthese |
|
|
717 | mismatches. The only thing it guarantees is that it starts decoding as |
|
|
718 | soon as a syntactically valid JSON text has been seen. This means you need |
|
|
719 | to set resource limits (e.g. C<max_size>) to ensure the parser will stop |
|
|
720 | parsing in the presence if syntax errors. |
|
|
721 | |
|
|
722 | The following methods implement this incremental parser. |
|
|
723 | |
|
|
724 | =over 4 |
|
|
725 | |
|
|
726 | =item [void, scalar or list context] = $json->incr_parse ([$string]) |
|
|
727 | |
|
|
728 | This is the central parsing function. It can both append new text and |
|
|
729 | extract objects from the stream accumulated so far (both of these |
|
|
730 | functions are optional). |
|
|
731 | |
|
|
732 | If C<$string> is given, then this string is appended to the already |
|
|
733 | existing JSON fragment stored in the C<$json> object. |
|
|
734 | |
|
|
735 | After that, if the function is called in void context, it will simply |
|
|
736 | return without doing anything further. This can be used to add more text |
|
|
737 | in as many chunks as you want. |
|
|
738 | |
|
|
739 | If the method is called in scalar context, then it will try to extract |
|
|
740 | exactly I<one> JSON object. If that is successful, it will return this |
|
|
741 | object, otherwise it will return C<undef>. If there is a parse error, |
|
|
742 | this method will croak just as C<decode> would do (one can then use |
|
|
743 | C<incr_skip> to skip the errornous part). This is the most common way of |
|
|
744 | using the method. |
|
|
745 | |
|
|
746 | And finally, in list context, it will try to extract as many objects |
|
|
747 | from the stream as it can find and return them, or the empty list |
|
|
748 | otherwise. For this to work, there must be no separators between the JSON |
|
|
749 | objects or arrays, instead they must be concatenated back-to-back. If |
|
|
750 | an error occurs, an exception will be raised as in the scalar context |
|
|
751 | case. Note that in this case, any previously-parsed JSON texts will be |
|
|
752 | lost. |
|
|
753 | |
|
|
754 | =item $lvalue_string = $json->incr_text |
|
|
755 | |
|
|
756 | This method returns the currently stored JSON fragment as an lvalue, that |
|
|
757 | is, you can manipulate it. This I<only> works when a preceding call to |
|
|
758 | C<incr_parse> in I<scalar context> successfully returned an object. Under |
|
|
759 | all other circumstances you must not call this function (I mean it. |
|
|
760 | although in simple tests it might actually work, it I<will> fail under |
|
|
761 | real world conditions). As a special exception, you can also call this |
|
|
762 | method before having parsed anything. |
|
|
763 | |
|
|
764 | This function is useful in two cases: a) finding the trailing text after a |
|
|
765 | JSON object or b) parsing multiple JSON objects separated by non-JSON text |
|
|
766 | (such as commas). |
|
|
767 | |
|
|
768 | =item $json->incr_skip |
|
|
769 | |
|
|
770 | This will reset the state of the incremental parser and will remove |
|
|
771 | the parsed text from the input buffer so far. This is useful after |
|
|
772 | C<incr_parse> died, in which case the input buffer and incremental parser |
|
|
773 | state is left unchanged, to skip the text parsed so far and to reset the |
|
|
774 | parse state. |
|
|
775 | |
|
|
776 | The difference to C<incr_reset> is that only text until the parse error |
|
|
777 | occured is removed. |
|
|
778 | |
|
|
779 | =item $json->incr_reset |
|
|
780 | |
|
|
781 | This completely resets the incremental parser, that is, after this call, |
|
|
782 | it will be as if the parser had never parsed anything. |
|
|
783 | |
|
|
784 | This is useful if you want to repeatedly parse JSON objects and want to |
|
|
785 | ignore any trailing data, which means you have to reset the parser after |
|
|
786 | each successful decode. |
|
|
787 | |
|
|
788 | =back |
|
|
789 | |
|
|
790 | =head2 LIMITATIONS |
|
|
791 | |
|
|
792 | All options that affect decoding are supported, except |
|
|
793 | C<allow_nonref>. The reason for this is that it cannot be made to |
|
|
794 | work sensibly: JSON objects and arrays are self-delimited, i.e. you can concatenate |
|
|
795 | them back to back and still decode them perfectly. This does not hold true |
|
|
796 | for JSON numbers, however. |
|
|
797 | |
|
|
798 | For example, is the string C<1> a single JSON number, or is it simply the |
|
|
799 | start of C<12>? Or is C<12> a single JSON number, or the concatenation |
|
|
800 | of C<1> and C<2>? In neither case you can tell, and this is why JSON::XS |
|
|
801 | takes the conservative route and disallows this case. |
|
|
802 | |
|
|
803 | =head2 EXAMPLES |
|
|
804 | |
|
|
805 | Some examples will make all this clearer. First, a simple example that |
|
|
806 | works similarly to C<decode_prefix>: We want to decode the JSON object at |
|
|
807 | the start of a string and identify the portion after the JSON object: |
|
|
808 | |
|
|
809 | my $text = "[1,2,3] hello"; |
|
|
810 | |
|
|
811 | my $json = new JSON::XS; |
|
|
812 | |
|
|
813 | my $obj = $json->incr_parse ($text) |
|
|
814 | or die "expected JSON object or array at beginning of string"; |
|
|
815 | |
|
|
816 | my $tail = $json->incr_text; |
|
|
817 | # $tail now contains " hello" |
|
|
818 | |
|
|
819 | Easy, isn't it? |
|
|
820 | |
|
|
821 | Now for a more complicated example: Imagine a hypothetical protocol where |
|
|
822 | you read some requests from a TCP stream, and each request is a JSON |
|
|
823 | array, without any separation between them (in fact, it is often useful to |
|
|
824 | use newlines as "separators", as these get interpreted as whitespace at |
|
|
825 | the start of the JSON text, which makes it possible to test said protocol |
|
|
826 | with C<telnet>...). |
|
|
827 | |
|
|
828 | Here is how you'd do it (it is trivial to write this in an event-based |
|
|
829 | manner): |
|
|
830 | |
|
|
831 | my $json = new JSON::XS; |
|
|
832 | |
|
|
833 | # read some data from the socket |
|
|
834 | while (sysread $socket, my $buf, 4096) { |
|
|
835 | |
|
|
836 | # split and decode as many requests as possible |
|
|
837 | for my $request ($json->incr_parse ($buf)) { |
|
|
838 | # act on the $request |
|
|
839 | } |
|
|
840 | } |
|
|
841 | |
|
|
842 | Another complicated example: Assume you have a string with JSON objects |
|
|
843 | or arrays, all separated by (optional) comma characters (e.g. C<[1],[2], |
|
|
844 | [3]>). To parse them, we have to skip the commas between the JSON texts, |
|
|
845 | and here is where the lvalue-ness of C<incr_text> comes in useful: |
|
|
846 | |
|
|
847 | my $text = "[1],[2], [3]"; |
|
|
848 | my $json = new JSON::XS; |
|
|
849 | |
|
|
850 | # void context, so no parsing done |
|
|
851 | $json->incr_parse ($text); |
|
|
852 | |
|
|
853 | # now extract as many objects as possible. note the |
|
|
854 | # use of scalar context so incr_text can be called. |
|
|
855 | while (my $obj = $json->incr_parse) { |
|
|
856 | # do something with $obj |
|
|
857 | |
|
|
858 | # now skip the optional comma |
|
|
859 | $json->incr_text =~ s/^ \s* , //x; |
|
|
860 | } |
|
|
861 | |
|
|
862 | Now lets go for a very complex example: Assume that you have a gigantic |
|
|
863 | JSON array-of-objects, many gigabytes in size, and you want to parse it, |
|
|
864 | but you cannot load it into memory fully (this has actually happened in |
|
|
865 | the real world :). |
|
|
866 | |
|
|
867 | Well, you lost, you have to implement your own JSON parser. But JSON::XS |
|
|
868 | can still help you: You implement a (very simple) array parser and let |
|
|
869 | JSON decode the array elements, which are all full JSON objects on their |
|
|
870 | own (this wouldn't work if the array elements could be JSON numbers, for |
|
|
871 | example): |
|
|
872 | |
|
|
873 | my $json = new JSON::XS; |
|
|
874 | |
|
|
875 | # open the monster |
|
|
876 | open my $fh, "<bigfile.json" |
|
|
877 | or die "bigfile: $!"; |
|
|
878 | |
|
|
879 | # first parse the initial "[" |
|
|
880 | for (;;) { |
|
|
881 | sysread $fh, my $buf, 65536 |
|
|
882 | or die "read error: $!"; |
|
|
883 | $json->incr_parse ($buf); # void context, so no parsing |
|
|
884 | |
|
|
885 | # Exit the loop once we found and removed(!) the initial "[". |
|
|
886 | # In essence, we are (ab-)using the $json object as a simple scalar |
|
|
887 | # we append data to. |
|
|
888 | last if $json->incr_text =~ s/^ \s* \[ //x; |
|
|
889 | } |
|
|
890 | |
|
|
891 | # now we have the skipped the initial "[", so continue |
|
|
892 | # parsing all the elements. |
|
|
893 | for (;;) { |
|
|
894 | # in this loop we read data until we got a single JSON object |
|
|
895 | for (;;) { |
|
|
896 | if (my $obj = $json->incr_parse) { |
|
|
897 | # do something with $obj |
|
|
898 | last; |
|
|
899 | } |
|
|
900 | |
|
|
901 | # add more data |
|
|
902 | sysread $fh, my $buf, 65536 |
|
|
903 | or die "read error: $!"; |
|
|
904 | $json->incr_parse ($buf); # void context, so no parsing |
|
|
905 | } |
|
|
906 | |
|
|
907 | # in this loop we read data until we either found and parsed the |
|
|
908 | # separating "," between elements, or the final "]" |
|
|
909 | for (;;) { |
|
|
910 | # first skip whitespace |
|
|
911 | $json->incr_text =~ s/^\s*//; |
|
|
912 | |
|
|
913 | # if we find "]", we are done |
|
|
914 | if ($json->incr_text =~ s/^\]//) { |
|
|
915 | print "finished.\n"; |
|
|
916 | exit; |
|
|
917 | } |
|
|
918 | |
|
|
919 | # if we find ",", we can continue with the next element |
|
|
920 | if ($json->incr_text =~ s/^,//) { |
|
|
921 | last; |
|
|
922 | } |
|
|
923 | |
|
|
924 | # if we find anything else, we have a parse error! |
|
|
925 | if (length $json->incr_text) { |
|
|
926 | die "parse error near ", $json->incr_text; |
|
|
927 | } |
|
|
928 | |
|
|
929 | # else add more data |
|
|
930 | sysread $fh, my $buf, 65536 |
|
|
931 | or die "read error: $!"; |
|
|
932 | $json->incr_parse ($buf); # void context, so no parsing |
|
|
933 | } |
|
|
934 | |
|
|
935 | This is a complex example, but most of the complexity comes from the fact |
|
|
936 | that we are trying to be correct (bear with me if I am wrong, I never ran |
|
|
937 | the above example :). |
|
|
938 | |
|
|
939 | |
|
|
940 | |
622 | =head1 MAPPING |
941 | =head1 MAPPING |
623 | |
942 | |
624 | This section describes how JSON::XS maps Perl values to JSON values and |
943 | This section describes how JSON::XS maps Perl values to JSON values and |
625 | vice versa. These mappings are designed to "do the right thing" in most |
944 | vice versa. These mappings are designed to "do the right thing" in most |
626 | circumstances automatically, preserving round-tripping characteristics |
945 | circumstances automatically, preserving round-tripping characteristics |
627 | (what you put in comes out as something equivalent). |
946 | (what you put in comes out as something equivalent). |
628 | |
947 | |
629 | For the more enlightened: note that in the following descriptions, |
948 | For the more enlightened: note that in the following descriptions, |
630 | lowercase I<perl> refers to the Perl interpreter, while uppcercase I<Perl> |
949 | lowercase I<perl> refers to the Perl interpreter, while uppercase I<Perl> |
631 | refers to the abstract Perl language itself. |
950 | refers to the abstract Perl language itself. |
632 | |
951 | |
633 | |
952 | |
634 | =head2 JSON -> PERL |
953 | =head2 JSON -> PERL |
635 | |
954 | |
636 | =over 4 |
955 | =over 4 |
637 | |
956 | |
638 | =item object |
957 | =item object |
639 | |
958 | |
640 | A JSON object becomes a reference to a hash in Perl. No ordering of object |
959 | A JSON object becomes a reference to a hash in Perl. No ordering of object |
641 | keys is preserved (JSON does not preserver object key ordering itself). |
960 | keys is preserved (JSON does not preserve object key ordering itself). |
642 | |
961 | |
643 | =item array |
962 | =item array |
644 | |
963 | |
645 | A JSON array becomes a reference to an array in Perl. |
964 | A JSON array becomes a reference to an array in Perl. |
646 | |
965 | |
… | |
… | |
654 | |
973 | |
655 | A JSON number becomes either an integer, numeric (floating point) or |
974 | A JSON number becomes either an integer, numeric (floating point) or |
656 | string scalar in perl, depending on its range and any fractional parts. On |
975 | string scalar in perl, depending on its range and any fractional parts. On |
657 | the Perl level, there is no difference between those as Perl handles all |
976 | the Perl level, there is no difference between those as Perl handles all |
658 | the conversion details, but an integer may take slightly less memory and |
977 | the conversion details, but an integer may take slightly less memory and |
659 | might represent more values exactly than (floating point) numbers. |
978 | might represent more values exactly than floating point numbers. |
660 | |
979 | |
661 | If the number consists of digits only, JSON::XS will try to represent |
980 | If the number consists of digits only, JSON::XS will try to represent |
662 | it as an integer value. If that fails, it will try to represent it as |
981 | it as an integer value. If that fails, it will try to represent it as |
663 | a numeric (floating point) value if that is possible without loss of |
982 | a numeric (floating point) value if that is possible without loss of |
664 | precision. Otherwise it will preserve the number as a string value. |
983 | precision. Otherwise it will preserve the number as a string value (in |
|
|
984 | which case you lose roundtripping ability, as the JSON number will be |
|
|
985 | re-encoded toa JSON string). |
665 | |
986 | |
666 | Numbers containing a fractional or exponential part will always be |
987 | Numbers containing a fractional or exponential part will always be |
667 | represented as numeric (floating point) values, possibly at a loss of |
988 | represented as numeric (floating point) values, possibly at a loss of |
668 | precision. |
989 | precision (in which case you might lose perfect roundtripping ability, but |
669 | |
990 | the JSON number will still be re-encoded as a JSON number). |
670 | This might create round-tripping problems as numbers might become strings, |
|
|
671 | but as Perl is typeless there is no other way to do it. |
|
|
672 | |
991 | |
673 | =item true, false |
992 | =item true, false |
674 | |
993 | |
675 | These JSON atoms become C<JSON::XS::true> and C<JSON::XS::false>, |
994 | These JSON atoms become C<JSON::XS::true> and C<JSON::XS::false>, |
676 | respectively. They are overloaded to act almost exactly like the numbers |
995 | respectively. They are overloaded to act almost exactly like the numbers |
677 | C<1> and C<0>. You can check wether a scalar is a JSON boolean by using |
996 | C<1> and C<0>. You can check whether a scalar is a JSON boolean by using |
678 | the C<JSON::XS::is_bool> function. |
997 | the C<JSON::XS::is_bool> function. |
679 | |
998 | |
680 | =item null |
999 | =item null |
681 | |
1000 | |
682 | A JSON null atom becomes C<undef> in Perl. |
1001 | A JSON null atom becomes C<undef> in Perl. |
… | |
… | |
713 | Other unblessed references are generally not allowed and will cause an |
1032 | Other unblessed references are generally not allowed and will cause an |
714 | exception to be thrown, except for references to the integers C<0> and |
1033 | exception to be thrown, except for references to the integers C<0> and |
715 | C<1>, which get turned into C<false> and C<true> atoms in JSON. You can |
1034 | C<1>, which get turned into C<false> and C<true> atoms in JSON. You can |
716 | also use C<JSON::XS::false> and C<JSON::XS::true> to improve readability. |
1035 | also use C<JSON::XS::false> and C<JSON::XS::true> to improve readability. |
717 | |
1036 | |
718 | to_json [\0,JSON::XS::true] # yields [false,true] |
1037 | encode_json [\0, JSON::XS::true] # yields [false,true] |
719 | |
1038 | |
720 | =item JSON::XS::true, JSON::XS::false |
1039 | =item JSON::XS::true, JSON::XS::false |
721 | |
1040 | |
722 | These special values become JSON true and JSON false values, |
1041 | These special values become JSON true and JSON false values, |
723 | respectively. You can also use C<\1> and C<\0> directly if you want. |
1042 | respectively. You can also use C<\1> and C<\0> directly if you want. |
724 | |
1043 | |
725 | =item blessed objects |
1044 | =item blessed objects |
726 | |
1045 | |
727 | Blessed objects are not allowed. JSON::XS currently tries to encode their |
1046 | Blessed objects are not directly representable in JSON. See the |
728 | underlying representation (hash- or arrayref), but this behaviour might |
1047 | C<allow_blessed> and C<convert_blessed> methods on various options on |
729 | change in future versions. |
1048 | how to deal with this: basically, you can choose between throwing an |
|
|
1049 | exception, encoding the reference as if it weren't blessed, or provide |
|
|
1050 | your own serialiser method. |
730 | |
1051 | |
731 | =item simple scalars |
1052 | =item simple scalars |
732 | |
1053 | |
733 | Simple Perl scalars (any scalar that is not a reference) are the most |
1054 | Simple Perl scalars (any scalar that is not a reference) are the most |
734 | difficult objects to encode: JSON::XS will encode undefined scalars as |
1055 | difficult objects to encode: JSON::XS will encode undefined scalars as |
735 | JSON null value, scalars that have last been used in a string context |
1056 | JSON C<null> values, scalars that have last been used in a string context |
736 | before encoding as JSON strings and anything else as number value: |
1057 | before encoding as JSON strings, and anything else as number value: |
737 | |
1058 | |
738 | # dump as number |
1059 | # dump as number |
739 | to_json [2] # yields [2] |
1060 | encode_json [2] # yields [2] |
740 | to_json [-3.0e17] # yields [-3e+17] |
1061 | encode_json [-3.0e17] # yields [-3e+17] |
741 | my $value = 5; to_json [$value] # yields [5] |
1062 | my $value = 5; encode_json [$value] # yields [5] |
742 | |
1063 | |
743 | # used as string, so dump as string |
1064 | # used as string, so dump as string |
744 | print $value; |
1065 | print $value; |
745 | to_json [$value] # yields ["5"] |
1066 | encode_json [$value] # yields ["5"] |
746 | |
1067 | |
747 | # undef becomes null |
1068 | # undef becomes null |
748 | to_json [undef] # yields [null] |
1069 | encode_json [undef] # yields [null] |
749 | |
1070 | |
750 | You can force the type to be a string by stringifying it: |
1071 | You can force the type to be a JSON string by stringifying it: |
751 | |
1072 | |
752 | my $x = 3.1; # some variable containing a number |
1073 | my $x = 3.1; # some variable containing a number |
753 | "$x"; # stringified |
1074 | "$x"; # stringified |
754 | $x .= ""; # another, more awkward way to stringify |
1075 | $x .= ""; # another, more awkward way to stringify |
755 | print $x; # perl does it for you, too, quite often |
1076 | print $x; # perl does it for you, too, quite often |
756 | |
1077 | |
757 | You can force the type to be a number by numifying it: |
1078 | You can force the type to be a JSON number by numifying it: |
758 | |
1079 | |
759 | my $x = "3"; # some variable containing a string |
1080 | my $x = "3"; # some variable containing a string |
760 | $x += 0; # numify it, ensuring it will be dumped as a number |
1081 | $x += 0; # numify it, ensuring it will be dumped as a number |
761 | $x *= 1; # same thing, the choise is yours. |
1082 | $x *= 1; # same thing, the choice is yours. |
762 | |
1083 | |
763 | You can not currently output JSON booleans or force the type in other, |
1084 | You can not currently force the type in other, less obscure, ways. Tell me |
764 | less obscure, ways. Tell me if you need this capability. |
1085 | if you need this capability (but don't forget to explain why it's needed |
|
|
1086 | :). |
765 | |
1087 | |
766 | =back |
1088 | =back |
767 | |
1089 | |
768 | |
1090 | |
769 | =head1 COMPARISON |
1091 | =head1 ENCODING/CODESET FLAG NOTES |
770 | |
1092 | |
771 | As already mentioned, this module was created because none of the existing |
1093 | The interested reader might have seen a number of flags that signify |
772 | JSON modules could be made to work correctly. First I will describe the |
1094 | encodings or codesets - C<utf8>, C<latin1> and C<ascii>. There seems to be |
773 | problems (or pleasures) I encountered with various existing JSON modules, |
1095 | some confusion on what these do, so here is a short comparison: |
774 | followed by some benchmark values. JSON::XS was designed not to suffer |
1096 | |
775 | from any of these problems or limitations. |
1097 | C<utf8> controls whether the JSON text created by C<encode> (and expected |
|
|
1098 | by C<decode>) is UTF-8 encoded or not, while C<latin1> and C<ascii> only |
|
|
1099 | control whether C<encode> escapes character values outside their respective |
|
|
1100 | codeset range. Neither of these flags conflict with each other, although |
|
|
1101 | some combinations make less sense than others. |
|
|
1102 | |
|
|
1103 | Care has been taken to make all flags symmetrical with respect to |
|
|
1104 | C<encode> and C<decode>, that is, texts encoded with any combination of |
|
|
1105 | these flag values will be correctly decoded when the same flags are used |
|
|
1106 | - in general, if you use different flag settings while encoding vs. when |
|
|
1107 | decoding you likely have a bug somewhere. |
|
|
1108 | |
|
|
1109 | Below comes a verbose discussion of these flags. Note that a "codeset" is |
|
|
1110 | simply an abstract set of character-codepoint pairs, while an encoding |
|
|
1111 | takes those codepoint numbers and I<encodes> them, in our case into |
|
|
1112 | octets. Unicode is (among other things) a codeset, UTF-8 is an encoding, |
|
|
1113 | and ISO-8859-1 (= latin 1) and ASCII are both codesets I<and> encodings at |
|
|
1114 | the same time, which can be confusing. |
776 | |
1115 | |
777 | =over 4 |
1116 | =over 4 |
778 | |
1117 | |
779 | =item JSON 1.07 |
1118 | =item C<utf8> flag disabled |
780 | |
1119 | |
781 | Slow (but very portable, as it is written in pure Perl). |
1120 | When C<utf8> is disabled (the default), then C<encode>/C<decode> generate |
|
|
1121 | and expect Unicode strings, that is, characters with high ordinal Unicode |
|
|
1122 | values (> 255) will be encoded as such characters, and likewise such |
|
|
1123 | characters are decoded as-is, no canges to them will be done, except |
|
|
1124 | "(re-)interpreting" them as Unicode codepoints or Unicode characters, |
|
|
1125 | respectively (to Perl, these are the same thing in strings unless you do |
|
|
1126 | funny/weird/dumb stuff). |
782 | |
1127 | |
783 | Undocumented/buggy Unicode handling (how JSON handles unicode values is |
1128 | This is useful when you want to do the encoding yourself (e.g. when you |
784 | undocumented. One can get far by feeding it unicode strings and doing |
1129 | want to have UTF-16 encoded JSON texts) or when some other layer does |
785 | en-/decoding oneself, but unicode escapes are not working properly). |
1130 | the encoding for you (for example, when printing to a terminal using a |
|
|
1131 | filehandle that transparently encodes to UTF-8 you certainly do NOT want |
|
|
1132 | to UTF-8 encode your data first and have Perl encode it another time). |
786 | |
1133 | |
787 | No roundtripping (strings get clobbered if they look like numbers, e.g. |
1134 | =item C<utf8> flag enabled |
788 | the string C<2.0> will encode to C<2.0> instead of C<"2.0">, and that will |
|
|
789 | decode into the number 2. |
|
|
790 | |
1135 | |
791 | =item JSON::PC 0.01 |
1136 | If the C<utf8>-flag is enabled, C<encode>/C<decode> will encode all |
|
|
1137 | characters using the corresponding UTF-8 multi-byte sequence, and will |
|
|
1138 | expect your input strings to be encoded as UTF-8, that is, no "character" |
|
|
1139 | of the input string must have any value > 255, as UTF-8 does not allow |
|
|
1140 | that. |
792 | |
1141 | |
793 | Very fast. |
1142 | The C<utf8> flag therefore switches between two modes: disabled means you |
|
|
1143 | will get a Unicode string in Perl, enabled means you get an UTF-8 encoded |
|
|
1144 | octet/binary string in Perl. |
794 | |
1145 | |
795 | Undocumented/buggy Unicode handling. |
1146 | =item C<latin1> or C<ascii> flags enabled |
796 | |
1147 | |
797 | No roundtripping. |
1148 | With C<latin1> (or C<ascii>) enabled, C<encode> will escape characters |
|
|
1149 | with ordinal values > 255 (> 127 with C<ascii>) and encode the remaining |
|
|
1150 | characters as specified by the C<utf8> flag. |
798 | |
1151 | |
799 | Has problems handling many Perl values (e.g. regex results and other magic |
1152 | If C<utf8> is disabled, then the result is also correctly encoded in those |
800 | values will make it croak). |
1153 | character sets (as both are proper subsets of Unicode, meaning that a |
|
|
1154 | Unicode string with all character values < 256 is the same thing as a |
|
|
1155 | ISO-8859-1 string, and a Unicode string with all character values < 128 is |
|
|
1156 | the same thing as an ASCII string in Perl). |
801 | |
1157 | |
802 | Does not even generate valid JSON (C<{1,2}> gets converted to C<{1:2}> |
1158 | If C<utf8> is enabled, you still get a correct UTF-8-encoded string, |
803 | which is not a valid JSON text. |
1159 | regardless of these flags, just some more characters will be escaped using |
|
|
1160 | C<\uXXXX> then before. |
804 | |
1161 | |
805 | Unmaintained (maintainer unresponsive for many months, bugs are not |
1162 | Note that ISO-8859-1-I<encoded> strings are not compatible with UTF-8 |
806 | getting fixed). |
1163 | encoding, while ASCII-encoded strings are. That is because the ISO-8859-1 |
|
|
1164 | encoding is NOT a subset of UTF-8 (despite the ISO-8859-1 I<codeset> being |
|
|
1165 | a subset of Unicode), while ASCII is. |
807 | |
1166 | |
808 | =item JSON::Syck 0.21 |
1167 | Surprisingly, C<decode> will ignore these flags and so treat all input |
|
|
1168 | values as governed by the C<utf8> flag. If it is disabled, this allows you |
|
|
1169 | to decode ISO-8859-1- and ASCII-encoded strings, as both strict subsets of |
|
|
1170 | Unicode. If it is enabled, you can correctly decode UTF-8 encoded strings. |
809 | |
1171 | |
810 | Very buggy (often crashes). |
1172 | So neither C<latin1> nor C<ascii> are incompatible with the C<utf8> flag - |
|
|
1173 | they only govern when the JSON output engine escapes a character or not. |
811 | |
1174 | |
812 | Very inflexible (no human-readable format supported, format pretty much |
1175 | The main use for C<latin1> is to relatively efficiently store binary data |
813 | undocumented. I need at least a format for easy reading by humans and a |
1176 | as JSON, at the expense of breaking compatibility with most JSON decoders. |
814 | single-line compact format for use in a protocol, and preferably a way to |
|
|
815 | generate ASCII-only JSON texts). |
|
|
816 | |
1177 | |
817 | Completely broken (and confusingly documented) Unicode handling (unicode |
1178 | The main use for C<ascii> is to force the output to not contain characters |
818 | escapes are not working properly, you need to set ImplicitUnicode to |
1179 | with values > 127, which means you can interpret the resulting string |
819 | I<different> values on en- and decoding to get symmetric behaviour). |
1180 | as UTF-8, ISO-8859-1, ASCII, KOI8-R or most about any character set and |
820 | |
1181 | 8-bit-encoding, and still get the same data structure back. This is useful |
821 | No roundtripping (simple cases work, but this depends on wether the scalar |
1182 | when your channel for JSON transfer is not 8-bit clean or the encoding |
822 | value was used in a numeric context or not). |
1183 | might be mangled in between (e.g. in mail), and works because ASCII is a |
823 | |
1184 | proper subset of most 8-bit and multibyte encodings in use in the world. |
824 | Dumping hashes may skip hash values depending on iterator state. |
|
|
825 | |
|
|
826 | Unmaintained (maintainer unresponsive for many months, bugs are not |
|
|
827 | getting fixed). |
|
|
828 | |
|
|
829 | Does not check input for validity (i.e. will accept non-JSON input and |
|
|
830 | return "something" instead of raising an exception. This is a security |
|
|
831 | issue: imagine two banks transfering money between each other using |
|
|
832 | JSON. One bank might parse a given non-JSON request and deduct money, |
|
|
833 | while the other might reject the transaction with a syntax error. While a |
|
|
834 | good protocol will at least recover, that is extra unnecessary work and |
|
|
835 | the transaction will still not succeed). |
|
|
836 | |
|
|
837 | =item JSON::DWIW 0.04 |
|
|
838 | |
|
|
839 | Very fast. Very natural. Very nice. |
|
|
840 | |
|
|
841 | Undocumented unicode handling (but the best of the pack. Unicode escapes |
|
|
842 | still don't get parsed properly). |
|
|
843 | |
|
|
844 | Very inflexible. |
|
|
845 | |
|
|
846 | No roundtripping. |
|
|
847 | |
|
|
848 | Does not generate valid JSON texts (key strings are often unquoted, empty keys |
|
|
849 | result in nothing being output) |
|
|
850 | |
|
|
851 | Does not check input for validity. |
|
|
852 | |
1185 | |
853 | =back |
1186 | =back |
854 | |
1187 | |
855 | |
1188 | |
|
|
1189 | =head2 JSON and ECMAscript |
|
|
1190 | |
|
|
1191 | JSON syntax is based on how literals are represented in javascript (the |
|
|
1192 | not-standardised predecessor of ECMAscript) which is presumably why it is |
|
|
1193 | called "JavaScript Object Notation". |
|
|
1194 | |
|
|
1195 | However, JSON is not a subset (and also not a superset of course) of |
|
|
1196 | ECMAscript (the standard) or javascript (whatever browsers actually |
|
|
1197 | implement). |
|
|
1198 | |
|
|
1199 | If you want to use javascript's C<eval> function to "parse" JSON, you |
|
|
1200 | might run into parse errors for valid JSON texts, or the resulting data |
|
|
1201 | structure might not be queryable: |
|
|
1202 | |
|
|
1203 | One of the problems is that U+2028 and U+2029 are valid characters inside |
|
|
1204 | JSON strings, but are not allowed in ECMAscript string literals, so the |
|
|
1205 | following Perl fragment will not output something that can be guaranteed |
|
|
1206 | to be parsable by javascript's C<eval>: |
|
|
1207 | |
|
|
1208 | use JSON::XS; |
|
|
1209 | |
|
|
1210 | print encode_json [chr 0x2028]; |
|
|
1211 | |
|
|
1212 | The right fix for this is to use a proper JSON parser in your javascript |
|
|
1213 | programs, and not rely on C<eval> (see for example Douglas Crockford's |
|
|
1214 | F<json2.js> parser). |
|
|
1215 | |
|
|
1216 | If this is not an option, you can, as a stop-gap measure, simply encode to |
|
|
1217 | ASCII-only JSON: |
|
|
1218 | |
|
|
1219 | use JSON::XS; |
|
|
1220 | |
|
|
1221 | print JSON::XS->new->ascii->encode ([chr 0x2028]); |
|
|
1222 | |
|
|
1223 | Note that this will enlarge the resulting JSON text quite a bit if you |
|
|
1224 | have many non-ASCII characters. You might be tempted to run some regexes |
|
|
1225 | to only escape U+2028 and U+2029, e.g.: |
|
|
1226 | |
|
|
1227 | # DO NOT USE THIS! |
|
|
1228 | my $json = JSON::XS->new->utf8->encode ([chr 0x2028]); |
|
|
1229 | $json =~ s/\xe2\x80\xa8/\\u2028/g; # escape U+2028 |
|
|
1230 | $json =~ s/\xe2\x80\xa9/\\u2029/g; # escape U+2029 |
|
|
1231 | print $json; |
|
|
1232 | |
|
|
1233 | Note that I<this is a bad idea>: the above only works for U+2028 and |
|
|
1234 | U+2029 and thus only for fully ECMAscript-compliant parsers. Many existing |
|
|
1235 | javascript implementations, however, have issues with other characters as |
|
|
1236 | well - using C<eval> naively simply I<will> cause problems. |
|
|
1237 | |
|
|
1238 | Another problem is that some javascript implementations reserve |
|
|
1239 | some property names for their own purposes (which probably makes |
|
|
1240 | them non-ECMAscript-compliant). For example, Iceweasel reserves the |
|
|
1241 | C<__proto__> property name for it's own purposes. |
|
|
1242 | |
|
|
1243 | If that is a problem, you could parse try to filter the resulting JSON |
|
|
1244 | output for these property strings, e.g.: |
|
|
1245 | |
|
|
1246 | $json =~ s/"__proto__"\s*:/"__proto__renamed":/g; |
|
|
1247 | |
|
|
1248 | This works because C<__proto__> is not valid outside of strings, so every |
|
|
1249 | occurence of C<"__proto__"\s*:> must be a string used as property name. |
|
|
1250 | |
|
|
1251 | If you know of other incompatibilities, please let me know. |
|
|
1252 | |
|
|
1253 | |
856 | =head2 JSON and YAML |
1254 | =head2 JSON and YAML |
857 | |
1255 | |
858 | You often hear that JSON is a subset (or a close subset) of YAML. This is, |
1256 | You often hear that JSON is a subset of YAML. This is, however, a mass |
859 | however, a mass hysteria and very far from the truth. In general, there is |
1257 | hysteria(*) and very far from the truth (as of the time of this writing), |
860 | no way to configure JSON::XS to output a data structure as valid YAML. |
1258 | so let me state it clearly: I<in general, there is no way to configure |
|
|
1259 | JSON::XS to output a data structure as valid YAML> that works in all |
|
|
1260 | cases. |
861 | |
1261 | |
862 | If you really must use JSON::XS to generate YAML, you should use this |
1262 | If you really must use JSON::XS to generate YAML, you should use this |
863 | algorithm (subject to change in future versions): |
1263 | algorithm (subject to change in future versions): |
864 | |
1264 | |
865 | my $to_yaml = JSON::XS->new->utf8->space_after (1); |
1265 | my $to_yaml = JSON::XS->new->utf8->space_after (1); |
866 | my $yaml = $to_yaml->encode ($ref) . "\n"; |
1266 | my $yaml = $to_yaml->encode ($ref) . "\n"; |
867 | |
1267 | |
868 | This will usually generate JSON texts that also parse as valid |
1268 | This will I<usually> generate JSON texts that also parse as valid |
869 | YAML. Please note that YAML has hardcoded limits on (simple) object key |
1269 | YAML. Please note that YAML has hardcoded limits on (simple) object key |
870 | lengths that JSON doesn't have, so you should make sure that your hash |
1270 | lengths that JSON doesn't have and also has different and incompatible |
|
|
1271 | unicode handling, so you should make sure that your hash keys are |
871 | keys are noticably shorter than the 1024 characters YAML allows. |
1272 | noticeably shorter than the 1024 "stream characters" YAML allows and that |
|
|
1273 | you do not have characters with codepoint values outside the Unicode BMP |
|
|
1274 | (basic multilingual page). YAML also does not allow C<\/> sequences in |
|
|
1275 | strings (which JSON::XS does not I<currently> generate, but other JSON |
|
|
1276 | generators might). |
872 | |
1277 | |
873 | There might be other incompatibilities that I am not aware of. In general |
1278 | There might be other incompatibilities that I am not aware of (or the YAML |
|
|
1279 | specification has been changed yet again - it does so quite often). In |
874 | you should not try to generate YAML with a JSON generator or vice versa, |
1280 | general you should not try to generate YAML with a JSON generator or vice |
875 | or try to parse JSON with a YAML parser or vice versa: chances are high |
1281 | versa, or try to parse JSON with a YAML parser or vice versa: chances are |
876 | that you will run into severe interoperability problems. |
1282 | high that you will run into severe interoperability problems when you |
|
|
1283 | least expect it. |
|
|
1284 | |
|
|
1285 | =over 4 |
|
|
1286 | |
|
|
1287 | =item (*) |
|
|
1288 | |
|
|
1289 | I have been pressured multiple times by Brian Ingerson (one of the |
|
|
1290 | authors of the YAML specification) to remove this paragraph, despite him |
|
|
1291 | acknowledging that the actual incompatibilities exist. As I was personally |
|
|
1292 | bitten by this "JSON is YAML" lie, I refused and said I will continue to |
|
|
1293 | educate people about these issues, so others do not run into the same |
|
|
1294 | problem again and again. After this, Brian called me a (quote)I<complete |
|
|
1295 | and worthless idiot>(unquote). |
|
|
1296 | |
|
|
1297 | In my opinion, instead of pressuring and insulting people who actually |
|
|
1298 | clarify issues with YAML and the wrong statements of some of its |
|
|
1299 | proponents, I would kindly suggest reading the JSON spec (which is not |
|
|
1300 | that difficult or long) and finally make YAML compatible to it, and |
|
|
1301 | educating users about the changes, instead of spreading lies about the |
|
|
1302 | real compatibility for many I<years> and trying to silence people who |
|
|
1303 | point out that it isn't true. |
|
|
1304 | |
|
|
1305 | =back |
877 | |
1306 | |
878 | |
1307 | |
879 | =head2 SPEED |
1308 | =head2 SPEED |
880 | |
1309 | |
881 | It seems that JSON::XS is surprisingly fast, as shown in the following |
1310 | It seems that JSON::XS is surprisingly fast, as shown in the following |
882 | tables. They have been generated with the help of the C<eg/bench> program |
1311 | tables. They have been generated with the help of the C<eg/bench> program |
883 | in the JSON::XS distribution, to make it easy to compare on your own |
1312 | in the JSON::XS distribution, to make it easy to compare on your own |
884 | system. |
1313 | system. |
885 | |
1314 | |
886 | First comes a comparison between various modules using a very short |
1315 | First comes a comparison between various modules using |
887 | single-line JSON string: |
1316 | a very short single-line JSON string (also available at |
|
|
1317 | L<http://dist.schmorp.de/misc/json/short.json>). |
888 | |
1318 | |
889 | {"method": "handleMessage", "params": ["user1", "we were just talking"], \ |
1319 | {"method": "handleMessage", "params": ["user1", |
890 | "id": null, "array":[1,11,234,-5,1e5,1e7, true, false]} |
1320 | "we were just talking"], "id": null, "array":[1,11,234,-5,1e5,1e7, |
|
|
1321 | true, false]} |
891 | |
1322 | |
892 | It shows the number of encodes/decodes per second (JSON::XS uses |
1323 | It shows the number of encodes/decodes per second (JSON::XS uses |
893 | the functional interface, while JSON::XS/2 uses the OO interface |
1324 | the functional interface, while JSON::XS/2 uses the OO interface |
894 | with pretty-printing and hashkey sorting enabled, JSON::XS/3 enables |
1325 | with pretty-printing and hashkey sorting enabled, JSON::XS/3 enables |
895 | shrink). Higher is better: |
1326 | shrink). Higher is better: |
896 | |
1327 | |
897 | Storable | 15779.925 | 14169.946 | |
|
|
898 | -----------+------------+------------+ |
|
|
899 | module | encode | decode | |
1328 | module | encode | decode | |
900 | -----------|------------|------------| |
1329 | -----------|------------|------------| |
901 | JSON | 4990.842 | 4088.813 | |
1330 | JSON 1.x | 4990.842 | 4088.813 | |
902 | JSON::DWIW | 51653.990 | 71575.154 | |
1331 | JSON::DWIW | 51653.990 | 71575.154 | |
903 | JSON::PC | 65948.176 | 74631.744 | |
1332 | JSON::PC | 65948.176 | 74631.744 | |
904 | JSON::PP | 8931.652 | 3817.168 | |
1333 | JSON::PP | 8931.652 | 3817.168 | |
905 | JSON::Syck | 24877.248 | 27776.848 | |
1334 | JSON::Syck | 24877.248 | 27776.848 | |
906 | JSON::XS | 388361.481 | 227951.304 | |
1335 | JSON::XS | 388361.481 | 227951.304 | |
… | |
… | |
908 | JSON::XS/3 | 338250.323 | 218453.333 | |
1337 | JSON::XS/3 | 338250.323 | 218453.333 | |
909 | Storable | 16500.016 | 135300.129 | |
1338 | Storable | 16500.016 | 135300.129 | |
910 | -----------+------------+------------+ |
1339 | -----------+------------+------------+ |
911 | |
1340 | |
912 | That is, JSON::XS is about five times faster than JSON::DWIW on encoding, |
1341 | That is, JSON::XS is about five times faster than JSON::DWIW on encoding, |
913 | about three times faster on decoding, and over fourty times faster |
1342 | about three times faster on decoding, and over forty times faster |
914 | than JSON, even with pretty-printing and key sorting. It also compares |
1343 | than JSON, even with pretty-printing and key sorting. It also compares |
915 | favourably to Storable for small amounts of data. |
1344 | favourably to Storable for small amounts of data. |
916 | |
1345 | |
917 | Using a longer test string (roughly 18KB, generated from Yahoo! Locals |
1346 | Using a longer test string (roughly 18KB, generated from Yahoo! Locals |
918 | search API (http://nanoref.com/yahooapis/mgPdGg): |
1347 | search API (L<http://dist.schmorp.de/misc/json/long.json>). |
919 | |
1348 | |
920 | module | encode | decode | |
1349 | module | encode | decode | |
921 | -----------|------------|------------| |
1350 | -----------|------------|------------| |
922 | JSON | 55.260 | 34.971 | |
1351 | JSON 1.x | 55.260 | 34.971 | |
923 | JSON::DWIW | 825.228 | 1082.513 | |
1352 | JSON::DWIW | 825.228 | 1082.513 | |
924 | JSON::PC | 3571.444 | 2394.829 | |
1353 | JSON::PC | 3571.444 | 2394.829 | |
925 | JSON::PP | 210.987 | 32.574 | |
1354 | JSON::PP | 210.987 | 32.574 | |
926 | JSON::Syck | 552.551 | 787.544 | |
1355 | JSON::Syck | 552.551 | 787.544 | |
927 | JSON::XS | 5780.463 | 4854.519 | |
1356 | JSON::XS | 5780.463 | 4854.519 | |
… | |
… | |
931 | -----------+------------+------------+ |
1360 | -----------+------------+------------+ |
932 | |
1361 | |
933 | Again, JSON::XS leads by far (except for Storable which non-surprisingly |
1362 | Again, JSON::XS leads by far (except for Storable which non-surprisingly |
934 | decodes faster). |
1363 | decodes faster). |
935 | |
1364 | |
936 | On large strings containing lots of high unicode characters, some modules |
1365 | On large strings containing lots of high Unicode characters, some modules |
937 | (such as JSON::PC) seem to decode faster than JSON::XS, but the result |
1366 | (such as JSON::PC) seem to decode faster than JSON::XS, but the result |
938 | will be broken due to missing (or wrong) unicode handling. Others refuse |
1367 | will be broken due to missing (or wrong) Unicode handling. Others refuse |
939 | to decode or encode properly, so it was impossible to prepare a fair |
1368 | to decode or encode properly, so it was impossible to prepare a fair |
940 | comparison table for that case. |
1369 | comparison table for that case. |
941 | |
1370 | |
942 | |
1371 | |
943 | =head1 SECURITY CONSIDERATIONS |
1372 | =head1 SECURITY CONSIDERATIONS |
… | |
… | |
949 | any buffer overflows. Obviously, this module should ensure that and I am |
1378 | any buffer overflows. Obviously, this module should ensure that and I am |
950 | trying hard on making that true, but you never know. |
1379 | trying hard on making that true, but you never know. |
951 | |
1380 | |
952 | Second, you need to avoid resource-starving attacks. That means you should |
1381 | Second, you need to avoid resource-starving attacks. That means you should |
953 | limit the size of JSON texts you accept, or make sure then when your |
1382 | limit the size of JSON texts you accept, or make sure then when your |
954 | resources run out, thats just fine (e.g. by using a separate process that |
1383 | resources run out, that's just fine (e.g. by using a separate process that |
955 | can crash safely). The size of a JSON text in octets or characters is |
1384 | can crash safely). The size of a JSON text in octets or characters is |
956 | usually a good indication of the size of the resources required to decode |
1385 | usually a good indication of the size of the resources required to decode |
957 | it into a Perl structure. While JSON::XS can check the size of the JSON |
1386 | it into a Perl structure. While JSON::XS can check the size of the JSON |
958 | text, it might be too late when you already have it in memory, so you |
1387 | text, it might be too late when you already have it in memory, so you |
959 | might want to check the size before you accept the string. |
1388 | might want to check the size before you accept the string. |
960 | |
1389 | |
961 | Third, JSON::XS recurses using the C stack when decoding objects and |
1390 | Third, JSON::XS recurses using the C stack when decoding objects and |
962 | arrays. The C stack is a limited resource: for instance, on my amd64 |
1391 | arrays. The C stack is a limited resource: for instance, on my amd64 |
963 | machine with 8MB of stack size I can decode around 180k nested arrays but |
1392 | machine with 8MB of stack size I can decode around 180k nested arrays but |
964 | only 14k nested JSON objects (due to perl itself recursing deeply on croak |
1393 | only 14k nested JSON objects (due to perl itself recursing deeply on croak |
965 | to free the temporary). If that is exceeded, the program crashes. to be |
1394 | to free the temporary). If that is exceeded, the program crashes. To be |
966 | conservative, the default nesting limit is set to 512. If your process |
1395 | conservative, the default nesting limit is set to 512. If your process |
967 | has a smaller stack, you should adjust this setting accordingly with the |
1396 | has a smaller stack, you should adjust this setting accordingly with the |
968 | C<max_depth> method. |
1397 | C<max_depth> method. |
969 | |
1398 | |
970 | And last but least, something else could bomb you that I forgot to think |
1399 | Something else could bomb you, too, that I forgot to think of. In that |
971 | of. In that case, you get to keep the pieces. I am always open for hints, |
1400 | case, you get to keep the pieces. I am always open for hints, though... |
972 | though... |
1401 | |
|
|
1402 | Also keep in mind that JSON::XS might leak contents of your Perl data |
|
|
1403 | structures in its error messages, so when you serialise sensitive |
|
|
1404 | information you might want to make sure that exceptions thrown by JSON::XS |
|
|
1405 | will not end up in front of untrusted eyes. |
973 | |
1406 | |
974 | If you are using JSON::XS to return packets to consumption |
1407 | If you are using JSON::XS to return packets to consumption |
975 | by javascript scripts in a browser you should have a look at |
1408 | by JavaScript scripts in a browser you should have a look at |
976 | L<http://jpsykes.com/47/practical-csrf-and-json-security> to see wether |
1409 | L<http://jpsykes.com/47/practical-csrf-and-json-security> to see whether |
977 | you are vulnerable to some common attack vectors (which really are browser |
1410 | you are vulnerable to some common attack vectors (which really are browser |
978 | design bugs, but it is still you who will have to deal with it, as major |
1411 | design bugs, but it is still you who will have to deal with it, as major |
979 | browser developers care only for features, not about doing security |
1412 | browser developers care only for features, not about getting security |
980 | right). |
1413 | right). |
981 | |
1414 | |
982 | |
1415 | |
983 | =head1 THREADS |
1416 | =head1 THREADS |
984 | |
1417 | |
985 | This module is I<not> guarenteed to be thread safe and there are no |
1418 | This module is I<not> guaranteed to be thread safe and there are no |
986 | plans to change this until Perl gets thread support (as opposed to the |
1419 | plans to change this until Perl gets thread support (as opposed to the |
987 | horribly slow so-called "threads" which are simply slow and bloated |
1420 | horribly slow so-called "threads" which are simply slow and bloated |
988 | process simulations - use fork, its I<much> faster, cheaper, better). |
1421 | process simulations - use fork, it's I<much> faster, cheaper, better). |
989 | |
1422 | |
990 | (It might actually work, but you ahve ben warned). |
1423 | (It might actually work, but you have been warned). |
991 | |
1424 | |
992 | |
1425 | |
993 | =head1 BUGS |
1426 | =head1 BUGS |
994 | |
1427 | |
995 | While the goal of this module is to be correct, that unfortunately does |
1428 | While the goal of this module is to be correct, that unfortunately does |
996 | not mean its bug-free, only that I think its design is bug-free. It is |
1429 | not mean it's bug-free, only that I think its design is bug-free. If you |
997 | still relatively early in its development. If you keep reporting bugs they |
1430 | keep reporting bugs they will be fixed swiftly, though. |
998 | will be fixed swiftly, though. |
|
|
999 | |
1431 | |
1000 | Please refrain from using rt.cpan.org or any other bug reporting |
1432 | Please refrain from using rt.cpan.org or any other bug reporting |
1001 | service. I put the contact address into my modules for a reason. |
1433 | service. I put the contact address into my modules for a reason. |
1002 | |
1434 | |
1003 | =cut |
1435 | =cut |
… | |
… | |
1023 | "--" => sub { $_[0] = ${$_[0]} - 1 }, |
1455 | "--" => sub { $_[0] = ${$_[0]} - 1 }, |
1024 | fallback => 1; |
1456 | fallback => 1; |
1025 | |
1457 | |
1026 | 1; |
1458 | 1; |
1027 | |
1459 | |
|
|
1460 | =head1 SEE ALSO |
|
|
1461 | |
|
|
1462 | The F<json_xs> command line utility for quick experiments. |
|
|
1463 | |
1028 | =head1 AUTHOR |
1464 | =head1 AUTHOR |
1029 | |
1465 | |
1030 | Marc Lehmann <schmorp@schmorp.de> |
1466 | Marc Lehmann <schmorp@schmorp.de> |
1031 | http://home.schmorp.de/ |
1467 | http://home.schmorp.de/ |
1032 | |
1468 | |