[ViewVC] Diff of: cvs/JSON-XS/XS.pm

Comparing JSON-XS/XS.pm (file contents):
Revision 1.22 by root, Sun Mar 25 02:37:00 2007 UTC vs.
Revision 1.24 by root, Thu Mar 29 01:27:36 2007 UTC

…		…
128	$perl_scalar = JSON::XS->new->utf8->decode ($json_text)	128	$perl_scalar = JSON::XS->new->utf8->decode ($json_text)
129		129
130	except being faster.	130	except being faster.
131		131
132	=back	132	=back
		133
133		134
134	=head1 OBJECT-ORIENTED INTERFACE	135	=head1 OBJECT-ORIENTED INTERFACE
135		136
136	The object oriented interface lets you configure your own encoding or	137	The object oriented interface lets you configure your own encoding or
137	decoding style, within the limits of supported formats.	138	decoding style, within the limits of supported formats.
…		…
283	=> "Hello, World!"	284	=> "Hello, World!"
284		285
285	=item $json = $json->shrink ([$enable])	286	=item $json = $json->shrink ([$enable])
286		287
287	Perl usually over-allocates memory a bit when allocating space for	288	Perl usually over-allocates memory a bit when allocating space for
288	strings. This flag optionally resizes strings generated by either	289	strings. This flag optionally resizes strings generated by either
289	C<encode> or C<decode> to their minimum size possible. This can save	290	C<encode> or C<decode> to their minimum size possible. This can save
290	memory when your JSON texts are either very very long or you have many	291	memory when your JSON texts are either very very long or you have many
291	short strings. It will also try to downgrade any strings to octet-form	292	short strings. It will also try to downgrade any strings to octet-form
292	if possible: perl stores strings internally either in an encoding called	293	if possible: perl stores strings internally either in an encoding called
293	UTF-X or in octet-form. The latter cannot store everything but uses less	294	UTF-X or in octet-form. The latter cannot store everything but uses less
294	space in general.	295	space in general (and some buggy Perl or C code might even rely on that
		296	internal representation being used).
295		297
		298	The actual definition of what shrink does might change in future versions,
		299	but it will always try to save space at the expense of time.
		300
296	If C<$enable> is true (or missing), the string returned by C<encode> will be shrunk-to-fit,	301	If C<$enable> is true (or missing), the string returned by C<encode> will
297	while all strings generated by C<decode> will also be shrunk-to-fit.	302	be shrunk-to-fit, while all strings generated by C<decode> will also be
		303	shrunk-to-fit.
298		304
299	If C<$enable> is false, then the normal perl allocation algorithms are used.	305	If C<$enable> is false, then the normal perl allocation algorithms are used.
300	If you work with your data, then this is likely to be faster.	306	If you work with your data, then this is likely to be faster.
301		307
302	In the future, this setting might control other things, such as converting	308	In the future, this setting might control other things, such as converting
303	strings that look like integers or floats into integers or floats	309	strings that look like integers or floats into integers or floats
304	internally (there is no difference on the Perl level), saving space.	310	internally (there is no difference on the Perl level), saving space.
		311
		312	=item $json = $json->max_depth ([$maximum_nesting_depth])
		313
		314	Sets the maximum nesting level (default C<8192>) accepted while encoding
		315	or decoding. If the JSON text or Perl data structure has an equal or
		316	higher nesting level then this limit, then the encoder and decoder will
		317	stop and croak at that point.
		318
		319	Nesting level is defined by number of hash- or arrayrefs that the encoder
		320	needs to traverse to reach a given point or the number of C<{> or C<[>
		321	characters without their matching closing parenthesis crossed to reach a
		322	given character in a string.
		323
		324	Setting the maximum depth to one disallows any nesting, so that ensures
		325	that the object is only a single hash/object or array.
		326
		327	The argument to C<max_depth> will be rounded up to the next nearest power
		328	of two.
		329
		330	See SECURITY CONSIDERATIONS, below, for more info on why this is useful.
305		331
306	=item $json_text = $json->encode ($perl_scalar)	332	=item $json_text = $json->encode ($perl_scalar)
307		333
308	Converts the given Perl data structure (a simple scalar or a reference	334	Converts the given Perl data structure (a simple scalar or a reference
309	to a hash or array) to its JSON representation. Simple scalars will be	335	to a hash or array) to its JSON representation. Simple scalars will be
…		…
320	JSON numbers and strings become simple Perl scalars. JSON arrays become	346	JSON numbers and strings become simple Perl scalars. JSON arrays become
321	Perl arrayrefs and JSON objects become Perl hashrefs. C<true> becomes	347	Perl arrayrefs and JSON objects become Perl hashrefs. C<true> becomes
322	C<1>, C<false> becomes C<0> and C<null> becomes C<undef>.	348	C<1>, C<false> becomes C<0> and C<null> becomes C<undef>.
323		349
324	=back	350	=back
		351
325		352
326	=head1 MAPPING	353	=head1 MAPPING
327		354
328	This section describes how JSON::XS maps Perl values to JSON values and	355	This section describes how JSON::XS maps Perl values to JSON values and
329	vice versa. These mappings are designed to "do the right thing" in most	356	vice versa. These mappings are designed to "do the right thing" in most
…		…
440	=item circular data structures	467	=item circular data structures
441		468
442	Those will be encoded until memory or stackspace runs out.	469	Those will be encoded until memory or stackspace runs out.
443		470
444	=back	471	=back
		472
445		473
446	=head1 COMPARISON	474	=head1 COMPARISON
447		475
448	As already mentioned, this module was created because none of the existing	476	As already mentioned, this module was created because none of the existing
449	JSON modules could be made to work correctly. First I will describe the	477	JSON modules could be made to work correctly. First I will describe the
…		…
578	(such as JSON::PC) seem to decode faster than JSON::XS, but the result	606	(such as JSON::PC) seem to decode faster than JSON::XS, but the result
579	will be broken due to missing (or wrong) unicode handling. Others refuse	607	will be broken due to missing (or wrong) unicode handling. Others refuse
580	to decode or encode properly, so it was impossible to prepare a fair	608	to decode or encode properly, so it was impossible to prepare a fair
581	comparison table for that case.	609	comparison table for that case.
582		610
583	=head1 RESOURCE LIMITS
584		611
585	JSON::XS does not impose any limits on the size of JSON texts or Perl	612	=head1 SECURITY CONSIDERATIONS
586	values they represent - if your machine can handle it, JSON::XS will	613
587	encode or decode it. Future versions might optionally impose structure	614	When you are using JSON in a protocol, talking to untrusted potentially
588	depth and memory use resource limits.	615	hostile creatures requires relatively few measures.
		616
		617	First of all, your JSON decoder should be secure, that is, should not have
		618	any buffer overflows. Obviously, this module should ensure that and I am
		619	trying hard on making that true, but you never know.
		620
		621	Second, you need to avoid resource-starving attacks. That means you should
		622	limit the size of JSON texts you accept, or make sure then when your
		623	resources run out, thats just fine (e.g. by using a separate process that
		624	can crash safely). The size of a JSON text in octets or characters is
		625	usually a good indication of the size of the resources required to decode
		626	it into a Perl structure.
		627
		628	Third, JSON::XS recurses using the C stack when decoding objects and
		629	arrays. The C stack is a limited resource: for instance, on my amd64
		630	machine with 8MB of stack size I can decode around 180k nested arrays
		631	but only 14k nested JSON objects. If that is exceeded, the program
		632	crashes. Thats why the default nesting limit is set to 8192. If your
		633	process has a smaller stack, you should adjust this setting accordingly
		634	with the C<max_depth> method.
		635
		636	And last but least, something else could bomb you that I forgot to think
		637	of. In that case, you get to keep the pieces. I am alway sopen for hints,
		638	though...
		639
589		640
590	=head1 BUGS	641	=head1 BUGS
591		642
592	While the goal of this module is to be correct, that unfortunately does	643	While the goal of this module is to be correct, that unfortunately does
593	not mean its bug-free, only that I think its design is bug-free. It is	644	not mean its bug-free, only that I think its design is bug-free. It is
594	still very young and not well-tested. If you keep reporting bugs they will	645	still relatively early in its development. If you keep reporting bugs they
595	be fixed swiftly, though.	646	will be fixed swiftly, though.
596		647
597	=cut	648	=cut
598		649
599	1;	650	1;
600		651

Diff Legend

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines

Comparing JSON-XS/XS.pm (file contents): Revision 1.22 by root, Sun Mar 25 02:37:00 2007 UTC vs. Revision 1.24 by root, Thu Mar 29 01:27:36 2007 UTC

Diff Legend

Comparing JSON-XS/XS.pm (file contents):
Revision 1.22 by root, Sun Mar 25 02:37:00 2007 UTC vs.
Revision 1.24 by root, Thu Mar 29 01:27:36 2007 UTC