--- JSON-XS/XS.pm 2008/03/19 02:52:15 1.84 +++ JSON-XS/XS.pm 2008/03/19 13:54:53 1.89 @@ -940,7 +940,8 @@ Pure Perl, which should be 100% compatible with JSON::XS, just a bit slower. -You cannot really lose by using this module. +You cannot really lose by using this module, especially as it tries very +hard to work even with ancient Perl versions, while JSON::XS does not. =item JSON 1.07 @@ -1082,8 +1083,9 @@ in the JSON::XS distribution, to make it easy to compare on your own system. -First comes a comparison between various modules using a very short -single-line JSON string: +First comes a comparison between various modules using +a very short single-line JSON string (also available at +L). {"method": "handleMessage", "params": ["user1", "we were just talking"], \ "id": null, "array":[1,11,234,-5,1e5,1e7, true, false]} @@ -1112,7 +1114,7 @@ favourably to Storable for small amounts of data. Using a longer test string (roughly 18KB, generated from Yahoo! Locals -search API (http://nanoref.com/yahooapis/mgPdGg): +search API (L). module | encode | decode | -----------|------------|------------| @@ -1164,9 +1166,13 @@ has a smaller stack, you should adjust this setting accordingly with the C method. -And last but least, something else could bomb you that I forgot to think -of. In that case, you get to keep the pieces. I am always open for hints, -though... +Something else could bomb you, too, that I forgot to think of. In that +case, you get to keep the pieces. I am always open for hints, though... + +Also keep in mind that JSON::XS might leak contents of your Perl data +structures in its error messages, so when you serialise sensitive +information you might want to make sure that exceptions thrown by JSON::XS +will not end up in front of untrusted eyes. If you are using JSON::XS to return packets to consumption by JavaScript scripts in a browser you should have a look at