| … | |
… | |
| 751 | objects or arrays, instead they must be concatenated back-to-back. If |
751 | objects or arrays, instead they must be concatenated back-to-back. If |
| 752 | an error occurs, an exception will be raised as in the scalar context |
752 | an error occurs, an exception will be raised as in the scalar context |
| 753 | case. Note that in this case, any previously-parsed JSON texts will be |
753 | case. Note that in this case, any previously-parsed JSON texts will be |
| 754 | lost. |
754 | lost. |
| 755 | |
755 | |
|
|
756 | Example: Parse some JSON arrays/objects in a given string and return |
|
|
757 | them. |
|
|
758 | |
|
|
759 | my @objs = JSON::XS->new->incr_parse ("[5][7][1,2]"); |
|
|
760 | |
| 756 | =item $lvalue_string = $json->incr_text |
761 | =item $lvalue_string = $json->incr_text |
| 757 | |
762 | |
| 758 | This method returns the currently stored JSON fragment as an lvalue, that |
763 | This method returns the currently stored JSON fragment as an lvalue, that |
| 759 | is, you can manipulate it. This I<only> works when a preceding call to |
764 | is, you can manipulate it. This I<only> works when a preceding call to |
| 760 | C<incr_parse> in I<scalar context> successfully returned an object. Under |
765 | C<incr_parse> in I<scalar context> successfully returned an object. Under |
| … | |
… | |
| 1324 | a very short single-line JSON string (also available at |
1329 | a very short single-line JSON string (also available at |
| 1325 | L<http://dist.schmorp.de/misc/json/short.json>). |
1330 | L<http://dist.schmorp.de/misc/json/short.json>). |
| 1326 | |
1331 | |
| 1327 | {"method": "handleMessage", "params": ["user1", |
1332 | {"method": "handleMessage", "params": ["user1", |
| 1328 | "we were just talking"], "id": null, "array":[1,11,234,-5,1e5,1e7, |
1333 | "we were just talking"], "id": null, "array":[1,11,234,-5,1e5,1e7, |
| 1329 | true, false]} |
1334 | 1, 0]} |
| 1330 | |
1335 | |
| 1331 | It shows the number of encodes/decodes per second (JSON::XS uses |
1336 | It shows the number of encodes/decodes per second (JSON::XS uses |
| 1332 | the functional interface, while JSON::XS/2 uses the OO interface |
1337 | the functional interface, while JSON::XS/2 uses the OO interface |
| 1333 | with pretty-printing and hashkey sorting enabled, JSON::XS/3 enables |
1338 | with pretty-printing and hashkey sorting enabled, JSON::XS/3 enables |
| 1334 | shrink). Higher is better: |
1339 | shrink. JSON::DWIW/DS uses the deserialise function, while JSON::DWIW::FJ |
|
|
1340 | uses the from_json method). Higher is better: |
| 1335 | |
1341 | |
| 1336 | module | encode | decode | |
1342 | module | encode | decode | |
| 1337 | -----------|------------|------------| |
1343 | --------------|------------|------------| |
| 1338 | JSON 1.x | 4990.842 | 4088.813 | |
1344 | JSON::DWIW/DS | 86302.551 | 102300.098 | |
| 1339 | JSON::DWIW | 51653.990 | 71575.154 | |
1345 | JSON::DWIW/FJ | 86302.551 | 75983.768 | |
| 1340 | JSON::PC | 65948.176 | 74631.744 | |
1346 | JSON::PP | 15827.562 | 6638.658 | |
| 1341 | JSON::PP | 8931.652 | 3817.168 | |
1347 | JSON::Syck | 63358.066 | 47662.545 | |
| 1342 | JSON::Syck | 24877.248 | 27776.848 | |
1348 | JSON::XS | 511500.488 | 511500.488 | |
| 1343 | JSON::XS | 388361.481 | 227951.304 | |
1349 | JSON::XS/2 | 291271.111 | 388361.481 | |
| 1344 | JSON::XS/2 | 227951.304 | 218453.333 | |
1350 | JSON::XS/3 | 361577.931 | 361577.931 | |
| 1345 | JSON::XS/3 | 338250.323 | 218453.333 | |
1351 | Storable | 66788.280 | 265462.278 | |
| 1346 | Storable | 16500.016 | 135300.129 | |
|
|
| 1347 | -----------+------------+------------+ |
1352 | --------------+------------+------------+ |
| 1348 | |
1353 | |
| 1349 | That is, JSON::XS is about five times faster than JSON::DWIW on encoding, |
1354 | That is, JSON::XS is almost six times faster than JSON::DWIW on encoding, |
| 1350 | about three times faster on decoding, and over forty times faster |
1355 | about five times faster on decoding, and over thirty to seventy times |
| 1351 | than JSON, even with pretty-printing and key sorting. It also compares |
1356 | faster than JSON's pure perl implementation. It also compares favourably |
| 1352 | favourably to Storable for small amounts of data. |
1357 | to Storable for small amounts of data. |
| 1353 | |
1358 | |
| 1354 | Using a longer test string (roughly 18KB, generated from Yahoo! Locals |
1359 | Using a longer test string (roughly 18KB, generated from Yahoo! Locals |
| 1355 | search API (L<http://dist.schmorp.de/misc/json/long.json>). |
1360 | search API (L<http://dist.schmorp.de/misc/json/long.json>). |
| 1356 | |
1361 | |
| 1357 | module | encode | decode | |
1362 | module | encode | decode | |
| 1358 | -----------|------------|------------| |
1363 | --------------|------------|------------| |
| 1359 | JSON 1.x | 55.260 | 34.971 | |
1364 | JSON::DWIW/DS | 1647.927 | 2673.916 | |
| 1360 | JSON::DWIW | 825.228 | 1082.513 | |
1365 | JSON::DWIW/FJ | 1630.249 | 2596.128 | |
| 1361 | JSON::PC | 3571.444 | 2394.829 | |
|
|
| 1362 | JSON::PP | 210.987 | 32.574 | |
1366 | JSON::PP | 400.640 | 62.311 | |
| 1363 | JSON::Syck | 552.551 | 787.544 | |
1367 | JSON::Syck | 1481.040 | 1524.869 | |
| 1364 | JSON::XS | 5780.463 | 4854.519 | |
1368 | JSON::XS | 20661.596 | 9541.183 | |
| 1365 | JSON::XS/2 | 3869.998 | 4798.975 | |
1369 | JSON::XS/2 | 10683.403 | 9416.938 | |
| 1366 | JSON::XS/3 | 5862.880 | 4798.975 | |
1370 | JSON::XS/3 | 20661.596 | 9400.054 | |
| 1367 | Storable | 4445.002 | 5235.027 | |
1371 | Storable | 19765.806 | 10000.725 | |
| 1368 | -----------+------------+------------+ |
1372 | --------------+------------+------------+ |
| 1369 | |
1373 | |
| 1370 | Again, JSON::XS leads by far (except for Storable which non-surprisingly |
1374 | Again, JSON::XS leads by far (except for Storable which non-surprisingly |
| 1371 | decodes faster). |
1375 | decodes a bit faster). |
| 1372 | |
1376 | |
| 1373 | On large strings containing lots of high Unicode characters, some modules |
1377 | On large strings containing lots of high Unicode characters, some modules |
| 1374 | (such as JSON::PC) seem to decode faster than JSON::XS, but the result |
1378 | (such as JSON::PC) seem to decode faster than JSON::XS, but the result |
| 1375 | will be broken due to missing (or wrong) Unicode handling. Others refuse |
1379 | will be broken due to missing (or wrong) Unicode handling. Others refuse |
| 1376 | to decode or encode properly, so it was impossible to prepare a fair |
1380 | to decode or encode properly, so it was impossible to prepare a fair |
