|
|
1 | =head1 NAME |
|
|
2 | |
1 | =encoding utf-8 |
3 | =encoding utf-8 |
2 | |
|
|
3 | =head1 NAME |
|
|
4 | |
4 | |
5 | JSON::XS - JSON serialising/deserialising, done correctly and fast |
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) |
… | |
… | |
103 | |
103 | |
104 | package JSON::XS; |
104 | package JSON::XS; |
105 | |
105 | |
106 | use strict; |
106 | use strict; |
107 | |
107 | |
108 | our $VERSION = '2.01'; |
108 | our $VERSION = '2.1'; |
109 | our @ISA = qw(Exporter); |
109 | our @ISA = qw(Exporter); |
110 | |
110 | |
111 | our @EXPORT = qw(encode_json decode_json to_json from_json); |
111 | our @EXPORT = qw(encode_json decode_json to_json from_json); |
112 | |
112 | |
113 | sub to_json($) { |
113 | sub to_json($) { |
… | |
… | |
245 | |
245 | |
246 | If C<$enable> is false, then the C<encode> method will not escape Unicode |
246 | If C<$enable> is false, then the C<encode> method will not escape Unicode |
247 | characters unless required by the JSON syntax or other flags. This results |
247 | characters unless required by the JSON syntax or other flags. This results |
248 | in a faster and more compact format. |
248 | in a faster and more compact format. |
249 | |
249 | |
|
|
250 | See also the section I<ENCODING/CODESET FLAG NOTES> later in this |
|
|
251 | document. |
|
|
252 | |
250 | The main use for this flag is to produce JSON texts that can be |
253 | The main use for this flag is to produce JSON texts that can be |
251 | transmitted over a 7-bit channel, as the encoded JSON texts will not |
254 | transmitted over a 7-bit channel, as the encoded JSON texts will not |
252 | contain any 8 bit characters. |
255 | contain any 8 bit characters. |
253 | |
256 | |
254 | JSON::XS->new->ascii (1)->encode ([chr 0x10401]) |
257 | JSON::XS->new->ascii (1)->encode ([chr 0x10401]) |
… | |
… | |
265 | will not be affected in any way by this flag, as C<decode> by default |
268 | will not be affected in any way by this flag, as C<decode> by default |
266 | expects Unicode, which is a strict superset of latin1. |
269 | expects Unicode, which is a strict superset of latin1. |
267 | |
270 | |
268 | If C<$enable> is false, then the C<encode> method will not escape Unicode |
271 | If C<$enable> is false, then the C<encode> method will not escape Unicode |
269 | characters unless required by the JSON syntax or other flags. |
272 | characters unless required by the JSON syntax or other flags. |
|
|
273 | |
|
|
274 | See also the section I<ENCODING/CODESET FLAG NOTES> later in this |
|
|
275 | document. |
270 | |
276 | |
271 | The main use for this flag is efficiently encoding binary data as JSON |
277 | The main use for this flag is efficiently encoding binary data as JSON |
272 | text, as most octets will not be escaped, resulting in a smaller encoded |
278 | text, as most octets will not be escaped, resulting in a smaller encoded |
273 | size. The disadvantage is that the resulting JSON text is encoded |
279 | size. The disadvantage is that the resulting JSON text is encoded |
274 | in latin1 (and must correctly be treated as such when storing and |
280 | in latin1 (and must correctly be treated as such when storing and |
… | |
… | |
293 | |
299 | |
294 | If C<$enable> is false, then the C<encode> method will return the JSON |
300 | If C<$enable> is false, then the C<encode> method will return the JSON |
295 | string as a (non-encoded) Unicode string, while C<decode> expects thus a |
301 | string as a (non-encoded) Unicode string, while C<decode> expects thus a |
296 | Unicode string. Any decoding or encoding (e.g. to UTF-8 or UTF-16) needs |
302 | Unicode string. Any decoding or encoding (e.g. to UTF-8 or UTF-16) needs |
297 | to be done yourself, e.g. using the Encode module. |
303 | to be done yourself, e.g. using the Encode module. |
|
|
304 | |
|
|
305 | See also the section I<ENCODING/CODESET FLAG NOTES> later in this |
|
|
306 | document. |
298 | |
307 | |
299 | Example, output UTF-16BE-encoded JSON: |
308 | Example, output UTF-16BE-encoded JSON: |
300 | |
309 | |
301 | use Encode; |
310 | use Encode; |
302 | $jsontext = encode "UTF-16BE", JSON::XS->new->encode ($object); |
311 | $jsontext = encode "UTF-16BE", JSON::XS->new->encode ($object); |
… | |
… | |
672 | => ([], 3) |
681 | => ([], 3) |
673 | |
682 | |
674 | =back |
683 | =back |
675 | |
684 | |
676 | |
685 | |
|
|
686 | =head1 INCREMENTAL PARSING |
|
|
687 | |
|
|
688 | [This section is still EXPERIMENTAL] |
|
|
689 | |
|
|
690 | In some cases, there is the need for incremental parsing of JSON |
|
|
691 | texts. While this module always has to keep both JSON text and resulting |
|
|
692 | Perl data structure in memory at one time, it does allow you to parse a |
|
|
693 | JSON stream incrementally. It does so by accumulating text until it has |
|
|
694 | a full JSON object, which it then can decode. This process is similar to |
|
|
695 | using C<decode_prefix> to see if a full JSON object is available, but is |
|
|
696 | much more efficient (JSON::XS will only attempt to parse the JSON text |
|
|
697 | once it is sure it has enough text to get a decisive result, using a very |
|
|
698 | simple but truly incremental parser). |
|
|
699 | |
|
|
700 | The following two methods deal with this. |
|
|
701 | |
|
|
702 | =over 4 |
|
|
703 | |
|
|
704 | =item [void, scalar or list context] = $json->incr_parse ([$string]) |
|
|
705 | |
|
|
706 | This is the central parsing function. It can both append new text and |
|
|
707 | extract objects from the stream accumulated so far (both of these |
|
|
708 | functions are optional). |
|
|
709 | |
|
|
710 | If C<$string> is given, then this string is appended to the already |
|
|
711 | existing JSON fragment stored in the C<$json> object. |
|
|
712 | |
|
|
713 | After that, if the function is called in void context, it will simply |
|
|
714 | return without doing anything further. This can be used to add more text |
|
|
715 | in as many chunks as you want. |
|
|
716 | |
|
|
717 | If the method is called in scalar context, then it will try to extract |
|
|
718 | exactly I<one> JSON object. If that is successful, it will return this |
|
|
719 | object, otherwise it will return C<undef>. This is the most common way of |
|
|
720 | using the method. |
|
|
721 | |
|
|
722 | And finally, in list context, it will try to extract as many objects |
|
|
723 | from the stream as it can find and return them, or the empty list |
|
|
724 | otherwise. For this to work, there must be no separators between the JSON |
|
|
725 | objects or arrays, instead they must be concatenated back-to-back. |
|
|
726 | |
|
|
727 | =item $lvalue_string = $json->incr_text |
|
|
728 | |
|
|
729 | This method returns the currently stored JSON fragment as an lvalue, that |
|
|
730 | is, you can manipulate it. This I<only> works when a preceding call to |
|
|
731 | C<incr_parse> in I<scalar context> successfully returned an object. Under |
|
|
732 | all other circumstances you must not call this function (I mean it. |
|
|
733 | although in simple tests it might actually work, it I<will> fail under |
|
|
734 | real world conditions). As a special exception, you can also call this |
|
|
735 | method before having parsed anything. |
|
|
736 | |
|
|
737 | This function is useful in two cases: a) finding the trailing text after a |
|
|
738 | JSON object or b) parsing multiple JSON objects separated by non-JSON text |
|
|
739 | (such as commas). |
|
|
740 | |
|
|
741 | =back |
|
|
742 | |
|
|
743 | =head2 LIMITATIONS |
|
|
744 | |
|
|
745 | All options that affect decoding are supported, except |
|
|
746 | C<allow_nonref>. The reason for this is that it cannot be made to |
|
|
747 | work sensibly: JSON objects and arrays are self-delimited, i.e. you can concatenate |
|
|
748 | them back to back and still decode them perfectly. This does not hold true |
|
|
749 | for JSON numbers, however. |
|
|
750 | |
|
|
751 | For example, is the string C<1> a single JSON number, or is it simply the |
|
|
752 | start of C<12>? Or is C<12> a single JSON number, or the concatenation |
|
|
753 | of C<1> and C<2>? In neither case you can tell, and this is why JSON::XS |
|
|
754 | takes the conservative route and disallows this case. |
|
|
755 | |
|
|
756 | =head2 EXAMPLES |
|
|
757 | |
|
|
758 | Some examples will make all this clearer. First, a simple example that |
|
|
759 | works similarly to C<decode_prefix>: We want to decode the JSON object at |
|
|
760 | the start of a string and identify the portion after the JSON object: |
|
|
761 | |
|
|
762 | my $text = "[1,2,3] hello"; |
|
|
763 | |
|
|
764 | my $json = new JSON::XS; |
|
|
765 | |
|
|
766 | my $obj = $json->incr_parse ($text) |
|
|
767 | or die "expected JSON object or array at beginning of string"; |
|
|
768 | |
|
|
769 | my $tail = $json->incr_text; |
|
|
770 | # $tail now contains " hello" |
|
|
771 | |
|
|
772 | Easy, isn't it? |
|
|
773 | |
|
|
774 | Now for a more complicated example: Imagine a hypothetical protocol where |
|
|
775 | you read some requests from a TCP stream, and each request is a JSON |
|
|
776 | array, without any separation between them (in fact, it is often useful to |
|
|
777 | use newlines as "separators", as these get interpreted as whitespace at |
|
|
778 | the start of the JSON text, which makes it possible to test said protocol |
|
|
779 | with C<telnet>...). |
|
|
780 | |
|
|
781 | Here is how you'd do it (it is trivial to write this in an event-based |
|
|
782 | manner): |
|
|
783 | |
|
|
784 | my $json = new JSON::XS; |
|
|
785 | |
|
|
786 | # read some data from the socket |
|
|
787 | while (sysread $socket, my $buf, 4096) { |
|
|
788 | |
|
|
789 | # split and decode as many requests as possible |
|
|
790 | for my $request ($json->incr_parse ($buf)) { |
|
|
791 | # act on the $request |
|
|
792 | } |
|
|
793 | } |
|
|
794 | |
|
|
795 | Another complicated example: Assume you have a string with JSON objects |
|
|
796 | or arrays, all separated by (optional) comma characters (e.g. C<[1],[2], |
|
|
797 | [3]>). To parse them, we have to skip the commas between the JSON texts, |
|
|
798 | and here is where the lvalue-ness of C<incr_text> comes in useful: |
|
|
799 | |
|
|
800 | my $text = "[1],[2], [3]"; |
|
|
801 | my $json = new JSON::XS; |
|
|
802 | |
|
|
803 | # void context, so no parsing done |
|
|
804 | $json->incr_parse ($text); |
|
|
805 | |
|
|
806 | # now extract as many objects as possible. note the |
|
|
807 | # use of scalar context so incr_text can be called. |
|
|
808 | while (my $obj = $json->incr_parse) { |
|
|
809 | # do something with $obj |
|
|
810 | |
|
|
811 | # now skip the optional comma |
|
|
812 | $json->incr_text =~ s/^ \s* , //x; |
|
|
813 | } |
|
|
814 | |
|
|
815 | Now lets go for a very complex example: Assume that you have a gigantic |
|
|
816 | JSON array-of-objects, many gigabytes in size, and you want to parse it, |
|
|
817 | but you cannot load it into memory fully (this has actually happened in |
|
|
818 | the real world :). |
|
|
819 | |
|
|
820 | Well, you lost, you have to implement your own JSON parser. But JSON::XS |
|
|
821 | can still help you: You implement a (very simple) array parser and let |
|
|
822 | JSON decode the array elements, which are all full JSON objects on their |
|
|
823 | own (this wouldn't work if the array elements could be JSON numbers, for |
|
|
824 | example): |
|
|
825 | |
|
|
826 | my $json = new JSON::XS; |
|
|
827 | |
|
|
828 | # open the monster |
|
|
829 | open my $fh, "<bigfile.json" |
|
|
830 | or die "bigfile: $!"; |
|
|
831 | |
|
|
832 | # first parse the initial "[" |
|
|
833 | for (;;) { |
|
|
834 | sysread $fh, my $buf, 65536 |
|
|
835 | or die "read error: $!"; |
|
|
836 | $json->incr_parse ($buf); # void context, so no parsing |
|
|
837 | |
|
|
838 | # Exit the loop once we found and removed(!) the initial "[". |
|
|
839 | # In essence, we are (ab-)using the $json object as a simple scalar |
|
|
840 | # we append data to. |
|
|
841 | last if $json->incr_text =~ s/^ \s* \[ //x; |
|
|
842 | } |
|
|
843 | |
|
|
844 | # now we have the skipped the initial "[", so continue |
|
|
845 | # parsing all the elements. |
|
|
846 | for (;;) { |
|
|
847 | # in this loop we read data until we got a single JSON object |
|
|
848 | for (;;) { |
|
|
849 | if (my $obj = $json->incr_parse) { |
|
|
850 | # do something with $obj |
|
|
851 | last; |
|
|
852 | } |
|
|
853 | |
|
|
854 | # add more data |
|
|
855 | sysread $fh, my $buf, 65536 |
|
|
856 | or die "read error: $!"; |
|
|
857 | $json->incr_parse ($buf); # void context, so no parsing |
|
|
858 | } |
|
|
859 | |
|
|
860 | # in this loop we read data until we either found and parsed the |
|
|
861 | # separating "," between elements, or the final "]" |
|
|
862 | for (;;) { |
|
|
863 | # first skip whitespace |
|
|
864 | $json->incr_text =~ s/^\s*//; |
|
|
865 | |
|
|
866 | # if we find "]", we are done |
|
|
867 | if ($json->incr_text =~ s/^\]//) { |
|
|
868 | print "finished.\n"; |
|
|
869 | exit; |
|
|
870 | } |
|
|
871 | |
|
|
872 | # if we find ",", we can continue with the next element |
|
|
873 | if ($json->incr_text =~ s/^,//) { |
|
|
874 | last; |
|
|
875 | } |
|
|
876 | |
|
|
877 | # if we find anything else, we have a parse error! |
|
|
878 | if (length $json->incr_text) { |
|
|
879 | die "parse error near ", $json->incr_text; |
|
|
880 | } |
|
|
881 | |
|
|
882 | # else add more data |
|
|
883 | sysread $fh, my $buf, 65536 |
|
|
884 | or die "read error: $!"; |
|
|
885 | $json->incr_parse ($buf); # void context, so no parsing |
|
|
886 | } |
|
|
887 | |
|
|
888 | This is a complex example, but most of the complexity comes from the fact |
|
|
889 | that we are trying to be correct (bear with me if I am wrong, I never ran |
|
|
890 | the above example :). |
|
|
891 | |
|
|
892 | |
|
|
893 | |
677 | =head1 MAPPING |
894 | =head1 MAPPING |
678 | |
895 | |
679 | This section describes how JSON::XS maps Perl values to JSON values and |
896 | This section describes how JSON::XS maps Perl values to JSON values and |
680 | vice versa. These mappings are designed to "do the right thing" in most |
897 | vice versa. These mappings are designed to "do the right thing" in most |
681 | circumstances automatically, preserving round-tripping characteristics |
898 | circumstances automatically, preserving round-tripping characteristics |
… | |
… | |
816 | my $x = "3"; # some variable containing a string |
1033 | my $x = "3"; # some variable containing a string |
817 | $x += 0; # numify it, ensuring it will be dumped as a number |
1034 | $x += 0; # numify it, ensuring it will be dumped as a number |
818 | $x *= 1; # same thing, the choice is yours. |
1035 | $x *= 1; # same thing, the choice is yours. |
819 | |
1036 | |
820 | You can not currently force the type in other, less obscure, ways. Tell me |
1037 | You can not currently force the type in other, less obscure, ways. Tell me |
821 | if you need this capability (but don't forget to explain why its needed |
1038 | if you need this capability (but don't forget to explain why it's needed |
822 | :). |
1039 | :). |
823 | |
1040 | |
824 | =back |
1041 | =back |
825 | |
1042 | |
826 | |
1043 | |
… | |
… | |
828 | |
1045 | |
829 | The interested reader might have seen a number of flags that signify |
1046 | The interested reader might have seen a number of flags that signify |
830 | encodings or codesets - C<utf8>, C<latin1> and C<ascii>. There seems to be |
1047 | encodings or codesets - C<utf8>, C<latin1> and C<ascii>. There seems to be |
831 | some confusion on what these do, so here is a short comparison: |
1048 | some confusion on what these do, so here is a short comparison: |
832 | |
1049 | |
833 | C<utf8> controls wether the JSON text created by C<encode> (and expected |
1050 | C<utf8> controls whether the JSON text created by C<encode> (and expected |
834 | by C<decode>) is UTF-8 encoded or not, while C<latin1> and C<ascii> only |
1051 | by C<decode>) is UTF-8 encoded or not, while C<latin1> and C<ascii> only |
835 | control wether C<encode> escapes character values outside their respective |
1052 | control whether C<encode> escapes character values outside their respective |
836 | codeset range. Neither of these flags conflict with each other, although |
1053 | codeset range. Neither of these flags conflict with each other, although |
837 | some combinations make less sense than others. |
1054 | some combinations make less sense than others. |
838 | |
1055 | |
839 | Care has been taken to make all flags symmetrical with respect to |
1056 | Care has been taken to make all flags symmetrical with respect to |
840 | C<encode> and C<decode>, that is, texts encoded with any combination of |
1057 | C<encode> and C<decode>, that is, texts encoded with any combination of |
… | |
… | |
1021 | |
1238 | |
1022 | |
1239 | |
1023 | =head2 JSON and YAML |
1240 | =head2 JSON and YAML |
1024 | |
1241 | |
1025 | You often hear that JSON is a subset of YAML. This is, however, a mass |
1242 | You often hear that JSON is a subset of YAML. This is, however, a mass |
1026 | hysteria(*) and very far from the truth. In general, there is no way to |
1243 | hysteria(*) and very far from the truth (as of the time of this writing), |
|
|
1244 | so let me state it clearly: I<in general, there is no way to configure |
1027 | configure JSON::XS to output a data structure as valid YAML that works for |
1245 | JSON::XS to output a data structure as valid YAML> that works in all |
1028 | all cases. |
1246 | cases. |
1029 | |
1247 | |
1030 | If you really must use JSON::XS to generate YAML, you should use this |
1248 | If you really must use JSON::XS to generate YAML, you should use this |
1031 | algorithm (subject to change in future versions): |
1249 | algorithm (subject to change in future versions): |
1032 | |
1250 | |
1033 | my $to_yaml = JSON::XS->new->utf8->space_after (1); |
1251 | my $to_yaml = JSON::XS->new->utf8->space_after (1); |
… | |
… | |
1036 | This will I<usually> generate JSON texts that also parse as valid |
1254 | This will I<usually> generate JSON texts that also parse as valid |
1037 | YAML. Please note that YAML has hardcoded limits on (simple) object key |
1255 | YAML. Please note that YAML has hardcoded limits on (simple) object key |
1038 | lengths that JSON doesn't have and also has different and incompatible |
1256 | lengths that JSON doesn't have and also has different and incompatible |
1039 | unicode handling, so you should make sure that your hash keys are |
1257 | unicode handling, so you should make sure that your hash keys are |
1040 | noticeably shorter than the 1024 "stream characters" YAML allows and that |
1258 | noticeably shorter than the 1024 "stream characters" YAML allows and that |
1041 | you do not have codepoints with values outside the Unicode BMP (basic |
1259 | you do not have characters with codepoint values outside the Unicode BMP |
1042 | multilingual page). YAML also does not allow C<\/> sequences in strings |
1260 | (basic multilingual page). YAML also does not allow C<\/> sequences in |
1043 | (which JSON::XS does not I<currently> generate). |
1261 | strings (which JSON::XS does not I<currently> generate, but other JSON |
|
|
1262 | generators might). |
1044 | |
1263 | |
1045 | There might be other incompatibilities that I am not aware of (or the YAML |
1264 | There might be other incompatibilities that I am not aware of (or the YAML |
1046 | specification has been changed yet again - it does so quite often). In |
1265 | specification has been changed yet again - it does so quite often). In |
1047 | general you should not try to generate YAML with a JSON generator or vice |
1266 | general you should not try to generate YAML with a JSON generator or vice |
1048 | versa, or try to parse JSON with a YAML parser or vice versa: chances are |
1267 | versa, or try to parse JSON with a YAML parser or vice versa: chances are |
… | |
… | |
1051 | |
1270 | |
1052 | =over 4 |
1271 | =over 4 |
1053 | |
1272 | |
1054 | =item (*) |
1273 | =item (*) |
1055 | |
1274 | |
1056 | This is spread actively by the YAML team, however. For many years now they |
1275 | I have been pressured multiple times by Brian Ingerson (one of the |
1057 | claim YAML were a superset of JSON, even when proven otherwise. |
1276 | authors of the YAML specification) to remove this paragraph, despite him |
|
|
1277 | acknowledging that the actual incompatibilities exist. As I was personally |
|
|
1278 | bitten by this "JSON is YAML" lie, I refused and said I will continue to |
|
|
1279 | educate people about these issues, so others do not run into the same |
|
|
1280 | problem again and again. After this, Brian called me a (quote)I<complete |
|
|
1281 | and worthless idiot>(unquote). |
1058 | |
1282 | |
1059 | Even the author of this manpage was at some point accused of providing |
1283 | In my opinion, instead of pressuring and insulting people who actually |
1060 | "incorrect" information, despite the evidence presented (claims ranged |
1284 | clarify issues with YAML and the wrong statements of some of its |
1061 | from "your documentation contains inaccurate and negative statements about |
1285 | proponents, I would kindly suggest reading the JSON spec (which is not |
1062 | YAML" (the only negative comment is this footnote, and it didn't exist |
1286 | that difficult or long) and finally make YAML compatible to it, and |
1063 | back then; the question on which claims were inaccurate was never answered |
1287 | educating users about the changes, instead of spreading lies about the |
1064 | etc.) to "the YAML spec is not up-to-date" (the *real* and supposedly |
1288 | real compatibility for many I<years> and trying to silence people who |
1065 | JSON-compatible spec is apparently not currently publicly available) |
1289 | point out that it isn't true. |
1066 | to actual requests to replace this section by *incorrect* information, |
|
|
1067 | suppressing information about the real problem). |
|
|
1068 | |
|
|
1069 | So whenever you are told that YAML was a superset of JSON, first check |
|
|
1070 | wether it is really true (it might be when you check it, but it certainly |
|
|
1071 | was not true when this was written). I would much prefer if the YAML team |
|
|
1072 | would spent their time on actually making JSON compatibility a truth |
|
|
1073 | (JSON, after all, has a very small and simple specification) instead of |
|
|
1074 | trying to lobby/force people into reporting untruths. |
|
|
1075 | |
1290 | |
1076 | =back |
1291 | =back |
1077 | |
1292 | |
1078 | |
1293 | |
1079 | =head2 SPEED |
1294 | =head2 SPEED |
… | |
… | |
1081 | It seems that JSON::XS is surprisingly fast, as shown in the following |
1296 | It seems that JSON::XS is surprisingly fast, as shown in the following |
1082 | tables. They have been generated with the help of the C<eg/bench> program |
1297 | tables. They have been generated with the help of the C<eg/bench> program |
1083 | in the JSON::XS distribution, to make it easy to compare on your own |
1298 | in the JSON::XS distribution, to make it easy to compare on your own |
1084 | system. |
1299 | system. |
1085 | |
1300 | |
1086 | First comes a comparison between various modules using a very short |
1301 | First comes a comparison between various modules using |
1087 | single-line JSON string: |
1302 | a very short single-line JSON string (also available at |
|
|
1303 | L<http://dist.schmorp.de/misc/json/short.json>). |
1088 | |
1304 | |
1089 | {"method": "handleMessage", "params": ["user1", "we were just talking"], \ |
1305 | {"method": "handleMessage", "params": ["user1", "we were just talking"], \ |
1090 | "id": null, "array":[1,11,234,-5,1e5,1e7, true, false]} |
1306 | "id": null, "array":[1,11,234,-5,1e5,1e7, true, false]} |
1091 | |
1307 | |
1092 | It shows the number of encodes/decodes per second (JSON::XS uses |
1308 | It shows the number of encodes/decodes per second (JSON::XS uses |
… | |
… | |
1111 | about three times faster on decoding, and over forty times faster |
1327 | about three times faster on decoding, and over forty times faster |
1112 | than JSON, even with pretty-printing and key sorting. It also compares |
1328 | than JSON, even with pretty-printing and key sorting. It also compares |
1113 | favourably to Storable for small amounts of data. |
1329 | favourably to Storable for small amounts of data. |
1114 | |
1330 | |
1115 | Using a longer test string (roughly 18KB, generated from Yahoo! Locals |
1331 | Using a longer test string (roughly 18KB, generated from Yahoo! Locals |
1116 | search API (http://nanoref.com/yahooapis/mgPdGg): |
1332 | search API (L<http://dist.schmorp.de/misc/json/long.json>). |
1117 | |
1333 | |
1118 | module | encode | decode | |
1334 | module | encode | decode | |
1119 | -----------|------------|------------| |
1335 | -----------|------------|------------| |
1120 | JSON 1.x | 55.260 | 34.971 | |
1336 | JSON 1.x | 55.260 | 34.971 | |
1121 | JSON::DWIW | 825.228 | 1082.513 | |
1337 | JSON::DWIW | 825.228 | 1082.513 | |
… | |
… | |
1185 | =head1 THREADS |
1401 | =head1 THREADS |
1186 | |
1402 | |
1187 | This module is I<not> guaranteed to be thread safe and there are no |
1403 | This module is I<not> guaranteed to be thread safe and there are no |
1188 | plans to change this until Perl gets thread support (as opposed to the |
1404 | plans to change this until Perl gets thread support (as opposed to the |
1189 | horribly slow so-called "threads" which are simply slow and bloated |
1405 | horribly slow so-called "threads" which are simply slow and bloated |
1190 | process simulations - use fork, its I<much> faster, cheaper, better). |
1406 | process simulations - use fork, it's I<much> faster, cheaper, better). |
1191 | |
1407 | |
1192 | (It might actually work, but you have been warned). |
1408 | (It might actually work, but you have been warned). |
1193 | |
1409 | |
1194 | |
1410 | |
1195 | =head1 BUGS |
1411 | =head1 BUGS |
1196 | |
1412 | |
1197 | While the goal of this module is to be correct, that unfortunately does |
1413 | While the goal of this module is to be correct, that unfortunately does |
1198 | not mean its bug-free, only that I think its design is bug-free. It is |
1414 | not mean it's bug-free, only that I think its design is bug-free. It is |
1199 | still relatively early in its development. If you keep reporting bugs they |
1415 | still relatively early in its development. If you keep reporting bugs they |
1200 | will be fixed swiftly, though. |
1416 | will be fixed swiftly, though. |
1201 | |
1417 | |
1202 | Please refrain from using rt.cpan.org or any other bug reporting |
1418 | Please refrain from using rt.cpan.org or any other bug reporting |
1203 | service. I put the contact address into my modules for a reason. |
1419 | service. I put the contact address into my modules for a reason. |
… | |
… | |
1225 | "--" => sub { $_[0] = ${$_[0]} - 1 }, |
1441 | "--" => sub { $_[0] = ${$_[0]} - 1 }, |
1226 | fallback => 1; |
1442 | fallback => 1; |
1227 | |
1443 | |
1228 | 1; |
1444 | 1; |
1229 | |
1445 | |
|
|
1446 | =head1 SEE ALSO |
|
|
1447 | |
|
|
1448 | The F<json_xs> command line utility for quick experiments. |
|
|
1449 | |
1230 | =head1 AUTHOR |
1450 | =head1 AUTHOR |
1231 | |
1451 | |
1232 | Marc Lehmann <schmorp@schmorp.de> |
1452 | Marc Lehmann <schmorp@schmorp.de> |
1233 | http://home.schmorp.de/ |
1453 | http://home.schmorp.de/ |
1234 | |
1454 | |