… | |
… | |
3 | JSON::XS - JSON serialising/deserialising, done correctly and fast |
3 | JSON::XS - JSON serialising/deserialising, done correctly and fast |
4 | |
4 | |
5 | =head1 SYNOPSIS |
5 | =head1 SYNOPSIS |
6 | |
6 | |
7 | use JSON::XS; |
7 | use JSON::XS; |
|
|
8 | |
|
|
9 | # exported functions, croak on error |
|
|
10 | |
|
|
11 | $utf8_encoded_json_text = to_json $perl_hash_or_arrayref; |
|
|
12 | $perl_hash_or_arrayref = from_json $utf8_encoded_json_text; |
|
|
13 | |
|
|
14 | # oo-interface |
|
|
15 | |
|
|
16 | $coder = JSON::XS->new->ascii->pretty->allow_nonref; |
|
|
17 | $pretty_printed_unencoded = $coder->encode ($perl_scalar); |
|
|
18 | $perl_scalar = $coder->decode ($unicode_json_text); |
8 | |
19 | |
9 | =head1 DESCRIPTION |
20 | =head1 DESCRIPTION |
10 | |
21 | |
11 | This module converts Perl data structures to JSON and vice versa. Its |
22 | This module converts Perl data structures to JSON and vice versa. Its |
12 | primary goal is to be I<correct> and its secondary goal is to be |
23 | primary goal is to be I<correct> and its secondary goal is to be |
… | |
… | |
18 | their maintainers are unresponsive, gone missing, or not listening to bug |
29 | their maintainers are unresponsive, gone missing, or not listening to bug |
19 | reports for other reasons. |
30 | reports for other reasons. |
20 | |
31 | |
21 | See COMPARISON, below, for a comparison to some other JSON modules. |
32 | See COMPARISON, below, for a comparison to some other JSON modules. |
22 | |
33 | |
|
|
34 | See MAPPING, below, on how JSON::XS maps perl values to JSON values and |
|
|
35 | vice versa. |
|
|
36 | |
23 | =head2 FEATURES |
37 | =head2 FEATURES |
24 | |
38 | |
25 | =over 4 |
39 | =over 4 |
26 | |
40 | |
27 | =item * correct handling of unicode issues |
41 | =item * correct handling of unicode issues |
28 | |
42 | |
29 | This module knows how to handle Unicode, and even documents how it does so. |
43 | This module knows how to handle Unicode, and even documents how and when |
|
|
44 | it does so. |
30 | |
45 | |
31 | =item * round-trip integrity |
46 | =item * round-trip integrity |
32 | |
47 | |
33 | When you serialise a perl data structure using only datatypes supported |
48 | When you serialise a perl data structure using only datatypes supported |
34 | by JSON, the deserialised data structure is identical on the Perl level. |
49 | by JSON, the deserialised data structure is identical on the Perl level. |
35 | (e.g. the string "2.0" doesn't suddenly become "2"). |
50 | (e.g. the string "2.0" doesn't suddenly become "2"). |
36 | |
51 | |
37 | =item * strict checking of JSON correctness |
52 | =item * strict checking of JSON correctness |
38 | |
53 | |
39 | There is no guessing, no generating of illegal JSON strings by default, |
54 | There is no guessing, no generating of illegal JSON strings by default, |
40 | and only JSON is accepted as input (the latter is a security feature). |
55 | and only JSON is accepted as input by default (the latter is a security |
|
|
56 | feature). |
41 | |
57 | |
42 | =item * fast |
58 | =item * fast |
43 | |
59 | |
44 | compared to other JSON modules, this module compares favourably. |
60 | Compared to other JSON modules, this module compares favourably in terms |
|
|
61 | of speed, too. |
45 | |
62 | |
46 | =item * simple to use |
63 | =item * simple to use |
47 | |
64 | |
48 | This module has both a simple functional interface as well as an OO |
65 | This module has both a simple functional interface as well as an OO |
49 | interface. |
66 | interface. |
50 | |
67 | |
51 | =item * reasonably versatile output formats |
68 | =item * reasonably versatile output formats |
52 | |
69 | |
53 | You can choose between the most compact format possible, a pure-ascii |
70 | You can choose between the most compact guarenteed single-line format |
54 | format, or a pretty-printed format. Or you can combine those features in |
71 | possible (nice for simple line-based protocols), a pure-ascii format (for |
|
|
72 | when your transport is not 8-bit clean), or a pretty-printed format (for |
|
|
73 | when you want to read that stuff). Or you can combine those features in |
55 | whatever way you like. |
74 | whatever way you like. |
56 | |
75 | |
57 | =back |
76 | =back |
58 | |
77 | |
59 | =cut |
78 | =cut |
60 | |
79 | |
61 | package JSON::XS; |
80 | package JSON::XS; |
62 | |
81 | |
63 | BEGIN { |
82 | BEGIN { |
64 | $VERSION = '0.2'; |
83 | $VERSION = '0.3'; |
65 | @ISA = qw(Exporter); |
84 | @ISA = qw(Exporter); |
66 | |
85 | |
67 | @EXPORT = qw(to_json from_json); |
86 | @EXPORT = qw(to_json from_json); |
68 | require Exporter; |
87 | require Exporter; |
69 | |
88 | |
… | |
… | |
82 | |
101 | |
83 | Converts the given Perl data structure (a simple scalar or a reference to |
102 | Converts the given Perl data structure (a simple scalar or a reference to |
84 | a hash or array) to a UTF-8 encoded, binary string (that is, the string contains |
103 | a hash or array) to a UTF-8 encoded, binary string (that is, the string contains |
85 | octets only). Croaks on error. |
104 | octets only). Croaks on error. |
86 | |
105 | |
87 | This function call is functionally identical to C<< JSON::XS->new->utf8 |
106 | This function call is functionally identical to C<< JSON::XS->new->utf8->encode ($perl_scalar) >>. |
88 | (1)->encode ($perl_scalar) >>. |
|
|
89 | |
107 | |
90 | =item $perl_scalar = from_json $json_string |
108 | =item $perl_scalar = from_json $json_string |
91 | |
109 | |
92 | The opposite of C<to_json>: expects an UTF-8 (binary) string and tries to |
110 | The opposite of C<to_json>: expects an UTF-8 (binary) string and tries to |
93 | parse that as an UTF-8 encoded JSON string, returning the resulting simple |
111 | parse that as an UTF-8 encoded JSON string, returning the resulting simple |
94 | scalar or reference. Croaks on error. |
112 | scalar or reference. Croaks on error. |
95 | |
113 | |
96 | This function call is functionally identical to C<< JSON::XS->new->utf8 |
114 | This function call is functionally identical to C<< JSON::XS->new->utf8->decode ($json_string) >>. |
97 | (1)->decode ($json_string) >>. |
|
|
98 | |
115 | |
99 | =back |
116 | =back |
100 | |
117 | |
101 | =head1 OBJECT-ORIENTED INTERFACE |
118 | =head1 OBJECT-ORIENTED INTERFACE |
102 | |
119 | |
… | |
… | |
114 | be chained: |
131 | be chained: |
115 | |
132 | |
116 | my $json = JSON::XS->new->utf8(1)->space_after(1)->encode ({a => [1,2]}) |
133 | my $json = JSON::XS->new->utf8(1)->space_after(1)->encode ({a => [1,2]}) |
117 | => {"a": [1, 2]} |
134 | => {"a": [1, 2]} |
118 | |
135 | |
119 | =item $json = $json->ascii ($enable) |
136 | =item $json = $json->ascii ([$enable]) |
120 | |
137 | |
121 | If C<$enable> is true, then the C<encode> method will not generate |
138 | If C<$enable> is true (or missing), then the C<encode> method will |
122 | characters outside the code range C<0..127>. Any unicode characters |
139 | not generate characters outside the code range C<0..127>. Any unicode |
123 | outside that range will be escaped using either a single \uXXXX (BMP |
140 | characters outside that range will be escaped using either a single |
124 | characters) or a double \uHHHH\uLLLLL escape sequence, as per RFC4627. |
141 | \uXXXX (BMP characters) or a double \uHHHH\uLLLLL escape sequence, as per |
|
|
142 | RFC4627. |
125 | |
143 | |
126 | If C<$enable> is false, then the C<encode> method will not escape Unicode |
144 | If C<$enable> is false, then the C<encode> method will not escape Unicode |
127 | characters unless necessary. |
145 | characters unless necessary. |
128 | |
146 | |
129 | JSON::XS->new->ascii (1)->encode (chr 0x10401) |
147 | JSON::XS->new->ascii (1)->encode (chr 0x10401) |
130 | => \ud801\udc01 |
148 | => \ud801\udc01 |
131 | |
149 | |
132 | =item $json = $json->utf8 ($enable) |
150 | =item $json = $json->utf8 ([$enable]) |
133 | |
151 | |
134 | If C<$enable> is true, then the C<encode> method will encode the JSON |
152 | If C<$enable> is true (or missing), then the C<encode> method will encode |
135 | string into UTF-8, as required by many protocols, while the C<decode> |
153 | the JSON string into UTF-8, as required by many protocols, while the |
136 | method expects to be handled an UTF-8-encoded string. Please note that |
154 | C<decode> method expects to be handled an UTF-8-encoded string. Please |
137 | UTF-8-encoded strings do not contain any characters outside the range |
155 | note that UTF-8-encoded strings do not contain any characters outside the |
138 | C<0..255>, they are thus useful for bytewise/binary I/O. |
156 | range C<0..255>, they are thus useful for bytewise/binary I/O. |
139 | |
157 | |
140 | If C<$enable> is false, then the C<encode> method will return the JSON |
158 | If C<$enable> is false, then the C<encode> method will return the JSON |
141 | string as a (non-encoded) unicode string, while C<decode> expects thus a |
159 | string as a (non-encoded) unicode string, while C<decode> expects thus a |
142 | unicode string. Any decoding or encoding (e.g. to UTF-8 or UTF-16) needs |
160 | unicode string. Any decoding or encoding (e.g. to UTF-8 or UTF-16) needs |
143 | to be done yourself, e.g. using the Encode module. |
161 | to be done yourself, e.g. using the Encode module. |
144 | |
162 | |
|
|
163 | Example, output UTF-16-encoded JSON: |
|
|
164 | |
145 | =item $json = $json->pretty ($enable) |
165 | =item $json = $json->pretty ([$enable]) |
146 | |
166 | |
147 | This enables (or disables) all of the C<indent>, C<space_before> and |
167 | This enables (or disables) all of the C<indent>, C<space_before> and |
148 | C<space_after> (and in the future possibly more) flags in one call to |
168 | C<space_after> (and in the future possibly more) flags in one call to |
149 | generate the most readable (or most compact) form possible. |
169 | generate the most readable (or most compact) form possible. |
|
|
170 | |
|
|
171 | Example, pretty-print some simple structure: |
150 | |
172 | |
151 | my $json = JSON::XS->new->pretty(1)->encode ({a => [1,2]}) |
173 | my $json = JSON::XS->new->pretty(1)->encode ({a => [1,2]}) |
152 | => |
174 | => |
153 | { |
175 | { |
154 | "a" : [ |
176 | "a" : [ |
155 | 1, |
177 | 1, |
156 | 2 |
178 | 2 |
157 | ] |
179 | ] |
158 | } |
180 | } |
159 | |
181 | |
160 | =item $json = $json->indent ($enable) |
182 | =item $json = $json->indent ([$enable]) |
161 | |
183 | |
162 | If C<$enable> is true, then the C<encode> method will use a multiline |
184 | If C<$enable> is true (or missing), then the C<encode> method will use a multiline |
163 | format as output, putting every array member or object/hash key-value pair |
185 | format as output, putting every array member or object/hash key-value pair |
164 | into its own line, identing them properly. |
186 | into its own line, identing them properly. |
165 | |
187 | |
166 | If C<$enable> is false, no newlines or indenting will be produced, and the |
188 | If C<$enable> is false, no newlines or indenting will be produced, and the |
167 | resulting JSON strings is guarenteed not to contain any C<newlines>. |
189 | resulting JSON strings is guarenteed not to contain any C<newlines>. |
168 | |
190 | |
169 | This setting has no effect when decoding JSON strings. |
191 | This setting has no effect when decoding JSON strings. |
170 | |
192 | |
171 | =item $json = $json->space_before ($enable) |
193 | =item $json = $json->space_before ([$enable]) |
172 | |
194 | |
173 | If C<$enable> is true, then the C<encode> method will add an extra |
195 | If C<$enable> is true (or missing), then the C<encode> method will add an extra |
174 | optional space before the C<:> separating keys from values in JSON objects. |
196 | optional space before the C<:> separating keys from values in JSON objects. |
175 | |
197 | |
176 | If C<$enable> is false, then the C<encode> method will not add any extra |
198 | If C<$enable> is false, then the C<encode> method will not add any extra |
177 | space at those places. |
199 | space at those places. |
178 | |
200 | |
179 | This setting has no effect when decoding JSON strings. You will also most |
201 | This setting has no effect when decoding JSON strings. You will also most |
180 | likely combine this setting with C<space_after>. |
202 | likely combine this setting with C<space_after>. |
181 | |
203 | |
|
|
204 | Example, space_before enabled, space_after and indent disabled: |
|
|
205 | |
|
|
206 | {"key" :"value"} |
|
|
207 | |
182 | =item $json = $json->space_after ($enable) |
208 | =item $json = $json->space_after ([$enable]) |
183 | |
209 | |
184 | If C<$enable> is true, then the C<encode> method will add an extra |
210 | If C<$enable> is true (or missing), then the C<encode> method will add an extra |
185 | optional space after the C<:> separating keys from values in JSON objects |
211 | optional space after the C<:> separating keys from values in JSON objects |
186 | and extra whitespace after the C<,> separating key-value pairs and array |
212 | and extra whitespace after the C<,> separating key-value pairs and array |
187 | members. |
213 | members. |
188 | |
214 | |
189 | If C<$enable> is false, then the C<encode> method will not add any extra |
215 | If C<$enable> is false, then the C<encode> method will not add any extra |
190 | space at those places. |
216 | space at those places. |
191 | |
217 | |
192 | This setting has no effect when decoding JSON strings. |
218 | This setting has no effect when decoding JSON strings. |
193 | |
219 | |
|
|
220 | Example, space_before and indent disabled, space_after enabled: |
|
|
221 | |
|
|
222 | {"key": "value"} |
|
|
223 | |
194 | =item $json = $json->canonical ($enable) |
224 | =item $json = $json->canonical ([$enable]) |
195 | |
225 | |
196 | If C<$enable> is true, then the C<encode> method will output JSON objects |
226 | If C<$enable> is true (or missing), then the C<encode> method will output JSON objects |
197 | by sorting their keys. This is adding a comparatively high overhead. |
227 | by sorting their keys. This is adding a comparatively high overhead. |
198 | |
228 | |
199 | If C<$enable> is false, then the C<encode> method will output key-value |
229 | If C<$enable> is false, then the C<encode> method will output key-value |
200 | pairs in the order Perl stores them (which will likely change between runs |
230 | pairs in the order Perl stores them (which will likely change between runs |
201 | of the same script). |
231 | of the same script). |
… | |
… | |
205 | the same hash migh be encoded differently even if contains the same data, |
235 | the same hash migh be encoded differently even if contains the same data, |
206 | as key-value pairs have no inherent ordering in Perl. |
236 | as key-value pairs have no inherent ordering in Perl. |
207 | |
237 | |
208 | This setting has no effect when decoding JSON strings. |
238 | This setting has no effect when decoding JSON strings. |
209 | |
239 | |
210 | =item $json = $json->allow_nonref ($enable) |
240 | =item $json = $json->allow_nonref ([$enable]) |
211 | |
241 | |
212 | If C<$enable> is true, then the C<encode> method can convert a |
242 | If C<$enable> is true (or missing), then the C<encode> method can convert a |
213 | non-reference into its corresponding string, number or null JSON value, |
243 | non-reference into its corresponding string, number or null JSON value, |
214 | which is an extension to RFC4627. Likewise, C<decode> will accept those JSON |
244 | which is an extension to RFC4627. Likewise, C<decode> will accept those JSON |
215 | values instead of croaking. |
245 | values instead of croaking. |
216 | |
246 | |
217 | If C<$enable> is false, then the C<encode> method will croak if it isn't |
247 | If C<$enable> is false, then the C<encode> method will croak if it isn't |
218 | passed an arrayref or hashref, as JSON strings must either be an object |
248 | passed an arrayref or hashref, as JSON strings must either be an object |
219 | or array. Likewise, C<decode> will croak if given something that is not a |
249 | or array. Likewise, C<decode> will croak if given something that is not a |
220 | JSON object or array. |
250 | JSON object or array. |
|
|
251 | |
|
|
252 | Example, encode a Perl scalar as JSON value with enabled C<allow_nonref>, |
|
|
253 | resulting in an invalid JSON text: |
|
|
254 | |
|
|
255 | JSON::XS->new->allow_nonref->encode ("Hello, World!") |
|
|
256 | => "Hello, World!" |
|
|
257 | |
|
|
258 | =item $json = $json->shrink ([$enable]) |
|
|
259 | |
|
|
260 | Perl usually over-allocates memory a bit when allocating space for |
|
|
261 | strings. This flag optionally resizes strings generated by either |
|
|
262 | C<encode> or C<decode> to their minimum size possible. This can save |
|
|
263 | memory when your JSON strings are either very very long or you have many |
|
|
264 | short strings. It will also try to downgrade any strings to octet-form |
|
|
265 | if possible: perl stores strings internally either in an encoding called |
|
|
266 | UTF-X or in octet-form. The latter cannot store everything but uses less |
|
|
267 | space in general. |
|
|
268 | |
|
|
269 | If C<$enable> is true (or missing), the string returned by C<encode> will be shrunk-to-fit, |
|
|
270 | while all strings generated by C<decode> will also be shrunk-to-fit. |
|
|
271 | |
|
|
272 | If C<$enable> is false, then the normal perl allocation algorithms are used. |
|
|
273 | If you work with your data, then this is likely to be faster. |
|
|
274 | |
|
|
275 | In the future, this setting might control other things, such as converting |
|
|
276 | strings that look like integers or floats into integers or floats |
|
|
277 | internally (there is no difference on the Perl level), saving space. |
221 | |
278 | |
222 | =item $json_string = $json->encode ($perl_scalar) |
279 | =item $json_string = $json->encode ($perl_scalar) |
223 | |
280 | |
224 | Converts the given Perl data structure (a simple scalar or a reference |
281 | Converts the given Perl data structure (a simple scalar or a reference |
225 | to a hash or array) to its JSON representation. Simple scalars will be |
282 | to a hash or array) to its JSON representation. Simple scalars will be |
… | |
… | |
234 | returning the resulting simple scalar or reference. Croaks on error. |
291 | returning the resulting simple scalar or reference. Croaks on error. |
235 | |
292 | |
236 | JSON numbers and strings become simple Perl scalars. JSON arrays become |
293 | JSON numbers and strings become simple Perl scalars. JSON arrays become |
237 | Perl arrayrefs and JSON objects become Perl hashrefs. C<true> becomes |
294 | Perl arrayrefs and JSON objects become Perl hashrefs. C<true> becomes |
238 | C<1>, C<false> becomes C<0> and C<null> becomes C<undef>. |
295 | C<1>, C<false> becomes C<0> and C<null> becomes C<undef>. |
|
|
296 | |
|
|
297 | =back |
|
|
298 | |
|
|
299 | =head1 MAPPING |
|
|
300 | |
|
|
301 | This section describes how JSON::XS maps Perl values to JSON values and |
|
|
302 | vice versa. These mappings are designed to "do the right thing" in most |
|
|
303 | circumstances automatically, preserving round-tripping characteristics |
|
|
304 | (what you put in comes out as something equivalent). |
|
|
305 | |
|
|
306 | For the more enlightened: note that in the following descriptions, |
|
|
307 | lowercase I<perl> refers to the Perl interpreter, while uppcercase I<Perl> |
|
|
308 | refers to the abstract Perl language itself. |
|
|
309 | |
|
|
310 | =head2 JSON -> PERL |
|
|
311 | |
|
|
312 | =over 4 |
|
|
313 | |
|
|
314 | =item object |
|
|
315 | |
|
|
316 | A JSON object becomes a reference to a hash in Perl. No ordering of object |
|
|
317 | keys is preserved. |
|
|
318 | |
|
|
319 | =item array |
|
|
320 | |
|
|
321 | A JSON array becomes a reference to an array in Perl. |
|
|
322 | |
|
|
323 | =item string |
|
|
324 | |
|
|
325 | A JSON string becomes a string scalar in Perl - Unicode codepoints in JSON |
|
|
326 | are represented by the same codepoints in the Perl string, so no manual |
|
|
327 | decoding is necessary. |
|
|
328 | |
|
|
329 | =item number |
|
|
330 | |
|
|
331 | A JSON number becomes either an integer or numeric (floating point) |
|
|
332 | scalar in perl, depending on its range and any fractional parts. On the |
|
|
333 | Perl level, there is no difference between those as Perl handles all the |
|
|
334 | conversion details, but an integer may take slightly less memory and might |
|
|
335 | represent more values exactly than (floating point) numbers. |
|
|
336 | |
|
|
337 | =item true, false |
|
|
338 | |
|
|
339 | These JSON atoms become C<0>, C<1>, respectively. Information is lost in |
|
|
340 | this process. Future versions might represent those values differently, |
|
|
341 | but they will be guarenteed to act like these integers would normally in |
|
|
342 | Perl. |
|
|
343 | |
|
|
344 | =item null |
|
|
345 | |
|
|
346 | A JSON null atom becomes C<undef> in Perl. |
|
|
347 | |
|
|
348 | =back |
|
|
349 | |
|
|
350 | =head2 PERL -> JSON |
|
|
351 | |
|
|
352 | The mapping from Perl to JSON is slightly more difficult, as Perl is a |
|
|
353 | truly typeless language, so we can only guess which JSON type is meant by |
|
|
354 | a Perl value. |
|
|
355 | |
|
|
356 | =over 4 |
|
|
357 | |
|
|
358 | =item hash references |
|
|
359 | |
|
|
360 | Perl hash references become JSON objects. As there is no inherent ordering |
|
|
361 | in hash keys, they will usually be encoded in a pseudo-random order that |
|
|
362 | can change between runs of the same program but stays generally the same |
|
|
363 | within the single run of a program. JSON::XS can optionally sort the hash |
|
|
364 | keys (determined by the I<canonical> flag), so the same datastructure |
|
|
365 | will serialise to the same JSON text (given same settings and version of |
|
|
366 | JSON::XS), but this incurs a runtime overhead. |
|
|
367 | |
|
|
368 | =item array references |
|
|
369 | |
|
|
370 | Perl array references become JSON arrays. |
|
|
371 | |
|
|
372 | =item blessed objects |
|
|
373 | |
|
|
374 | Blessed objects are not allowed. JSON::XS currently tries to encode their |
|
|
375 | underlying representation (hash- or arrayref), but this behaviour might |
|
|
376 | change in future versions. |
|
|
377 | |
|
|
378 | =item simple scalars |
|
|
379 | |
|
|
380 | Simple Perl scalars (any scalar that is not a reference) are the most |
|
|
381 | difficult objects to encode: JSON::XS will encode undefined scalars as |
|
|
382 | JSON null value, scalars that have last been used in a string context |
|
|
383 | before encoding as JSON strings and anything else as number value: |
|
|
384 | |
|
|
385 | # dump as number |
|
|
386 | to_json [2] # yields [2] |
|
|
387 | to_json [-3.0e17] # yields [-3e+17] |
|
|
388 | my $value = 5; to_json [$value] # yields [5] |
|
|
389 | |
|
|
390 | # used as string, so dump as string |
|
|
391 | print $value; |
|
|
392 | to_json [$value] # yields ["5"] |
|
|
393 | |
|
|
394 | # undef becomes null |
|
|
395 | to_json [undef] # yields [null] |
|
|
396 | |
|
|
397 | You can force the type to be a string by stringifying it: |
|
|
398 | |
|
|
399 | my $x = 3.1; # some variable containing a number |
|
|
400 | "$x"; # stringified |
|
|
401 | $x .= ""; # another, more awkward way to stringify |
|
|
402 | print $x; # perl does it for you, too, quite often |
|
|
403 | |
|
|
404 | You can force the type to be a number by numifying it: |
|
|
405 | |
|
|
406 | my $x = "3"; # some variable containing a string |
|
|
407 | $x += 0; # numify it, ensuring it will be dumped as a number |
|
|
408 | $x *= 1; # same thing, the choise is yours. |
|
|
409 | |
|
|
410 | You can not currently output JSON booleans or force the type in other, |
|
|
411 | less obscure, ways. Tell me if you need this capability. |
|
|
412 | |
|
|
413 | =item circular data structures |
|
|
414 | |
|
|
415 | Those will be encoded until memory or stackspace runs out. |
239 | |
416 | |
240 | =back |
417 | =back |
241 | |
418 | |
242 | =head1 COMPARISON |
419 | =head1 COMPARISON |
243 | |
420 | |
… | |
… | |
364 | -----------+------------+------------+ |
541 | -----------+------------+------------+ |
365 | |
542 | |
366 | Again, JSON::XS leads by far in the encoding case, while still beating |
543 | Again, JSON::XS leads by far in the encoding case, while still beating |
367 | every other module in the decoding case. |
544 | every other module in the decoding case. |
368 | |
545 | |
369 | Last example is an almost 8MB large hash with many large binary values |
546 | =head1 RESOURCE LIMITS |
370 | (PNG files), resulting in a lot of escaping: |
547 | |
|
|
548 | JSON::XS does not impose any limits on the size of JSON texts or Perl |
|
|
549 | values they represent - if your machine can handle it, JSON::XS will |
|
|
550 | encode or decode it. Future versions might optionally impose structure |
|
|
551 | depth and memory use resource limits. |
371 | |
552 | |
372 | =head1 BUGS |
553 | =head1 BUGS |
373 | |
554 | |
374 | While the goal of this module is to be correct, that unfortunately does |
555 | While the goal of this module is to be correct, that unfortunately does |
375 | not mean its bug-free, only that I think its design is bug-free. It is |
556 | not mean its bug-free, only that I think its design is bug-free. It is |