ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/CBOR-XS/XS.pm
(Generate patch)

Comparing CBOR-XS/XS.pm (file contents):
Revision 1.20 by root, Wed Nov 20 02:03:08 2013 UTC vs.
Revision 1.31 by root, Sat Nov 30 18:13:53 2013 UTC

26 substr $many_cbor_strings, 0, $length, ""; # remove decoded cbor string 26 substr $many_cbor_strings, 0, $length, ""; # remove decoded cbor string
27 } 27 }
28 28
29=head1 DESCRIPTION 29=head1 DESCRIPTION
30 30
31WARNING! This module is very new, and not very well tested (that's up to
32you to do). Furthermore, details of the implementation might change freely
33before version 1.0. And lastly, the object serialisation protocol depends
34on a pending IANA assignment, and until that assignment is official, this
35implementation is not interoperable with other implementations (even
36future versions of this module) until the assignment is done.
37
38You are still invited to try out CBOR, and this module.
39
40This module converts Perl data structures to the Concise Binary Object 31This module converts Perl data structures to the Concise Binary Object
41Representation (CBOR) and vice versa. CBOR is a fast binary serialisation 32Representation (CBOR) and vice versa. CBOR is a fast binary serialisation
42format that aims to use a superset of the JSON data model, i.e. when you 33format that aims to use an (almost) superset of the JSON data model, i.e.
43can represent something in JSON, you should be able to represent it in 34when you can represent something useful in JSON, you should be able to
44CBOR. 35represent it in CBOR.
45 36
46In short, CBOR is a faster and very compact binary alternative to JSON, 37In short, CBOR is a faster and quite compact binary alternative to JSON,
47with the added ability of supporting serialisation of Perl objects. (JSON 38with the added ability of supporting serialisation of Perl objects. (JSON
48often compresses better than CBOR though, so if you plan to compress the 39often compresses better than CBOR though, so if you plan to compress the
49data later you might want to compare both formats first). 40data later and speed is less important you might want to compare both
41formats first).
50 42
51To give you a general idea about speed, with texts in the megabyte range, 43To give you a general idea about speed, with texts in the megabyte range,
52C<CBOR::XS> usually encodes roughly twice as fast as L<Storable> or 44C<CBOR::XS> usually encodes roughly twice as fast as L<Storable> or
53L<JSON::XS> and decodes about 15%-30% faster than those. The shorter the 45L<JSON::XS> and decodes about 15%-30% faster than those. The shorter the
54data, the worse L<Storable> performs in comparison. 46data, the worse L<Storable> performs in comparison.
55 47
56As for compactness, C<CBOR::XS> encoded data structures are usually about 48Regarding compactness, C<CBOR::XS>-encoded data structures are usually
5720% smaller than the same data encoded as (compact) JSON or L<Storable>. 49about 20% smaller than the same data encoded as (compact) JSON or
50L<Storable>.
51
52In addition to the core CBOR data format, this module implements a
53number of extensions, to support cyclic and shared data structures
54(see C<allow_sharing> and C<allow_cycles>), string deduplication (see
55C<pack_strings>) and scalar references (always enabled).
58 56
59The primary goal of this module is to be I<correct> and the secondary goal 57The primary goal of this module is to be I<correct> and the secondary goal
60is to be I<fast>. To reach the latter goal it was written in C. 58is to be I<fast>. To reach the latter goal it was written in C.
61 59
62See MAPPING, below, on how CBOR::XS maps perl values to CBOR values and 60See MAPPING, below, on how CBOR::XS maps perl values to CBOR values and
66 64
67package CBOR::XS; 65package CBOR::XS;
68 66
69use common::sense; 67use common::sense;
70 68
71our $VERSION = 0.08; 69our $VERSION = '1.0';
72our @ISA = qw(Exporter); 70our @ISA = qw(Exporter);
73 71
74our @EXPORT = qw(encode_cbor decode_cbor); 72our @EXPORT = qw(encode_cbor decode_cbor);
75 73
76use Exporter; 74use Exporter;
113strings. All boolean flags described below are by default I<disabled>. 111strings. All boolean flags described below are by default I<disabled>.
114 112
115The mutators for flags all return the CBOR object again and thus calls can 113The mutators for flags all return the CBOR object again and thus calls can
116be chained: 114be chained:
117 115
118#TODO
119 my $cbor = CBOR::XS->new->encode ({a => [1,2]}); 116 my $cbor = CBOR::XS->new->encode ({a => [1,2]});
120 117
121=item $cbor = $cbor->max_depth ([$maximum_nesting_depth]) 118=item $cbor = $cbor->max_depth ([$maximum_nesting_depth])
122 119
123=item $max_depth = $cbor->get_max_depth 120=item $max_depth = $cbor->get_max_depth
182as an array, is referenced multiple times), but instead will emit a 179as an array, is referenced multiple times), but instead will emit a
183reference to the earlier value. 180reference to the earlier value.
184 181
185This means that such values will only be encoded once, and will not result 182This means that such values will only be encoded once, and will not result
186in a deep cloning of the value on decode, in decoders supporting the value 183in a deep cloning of the value on decode, in decoders supporting the value
187sharing extension. 184sharing extension. This also makes it possible to encode cyclic data
185structures (which need C<allow_cycles> to ne enabled to be decoded by this
186module).
187
188It is recommended to leave it off unless you know your
189communication partner supports the value sharing extensions to CBOR
190(L<http://cbor.schmorp.de/value-sharing>), as without decoder support, the
191resulting data structure might be unusable.
188 192
189Detecting shared values incurs a runtime overhead when values are encoded 193Detecting shared values incurs a runtime overhead when values are encoded
190that have a reference counter large than one, and might unnecessarily 194that have a reference counter large than one, and might unnecessarily
191increase the encoded size, as potentially shared values are encode as 195increase the encoded size, as potentially shared values are encode as
192sharable whether or not they are actually shared. 196shareable whether or not they are actually shared.
193 197
194At the moment, only targets of references can be shared (e.g. scalars, 198At the moment, only targets of references can be shared (e.g. scalars,
195arrays or hashes pointed to by a reference). Weirder constructs, such as 199arrays or hashes pointed to by a reference). Weirder constructs, such as
196an array with multiple "copies" of the I<same> string, which are hard but 200an array with multiple "copies" of the I<same> string, which are hard but
197not impossible to create in Perl, are not supported (this is the same as 201not impossible to create in Perl, are not supported (this is the same as
198for L<Storable>). 202with L<Storable>).
199 203
200If C<$enable> is false (the default), then C<encode> will encode 204If C<$enable> is false (the default), then C<encode> will encode shared
201exception when it encounters anything it cannot encode as CBOR. 205data structures repeatedly, unsharing them in the process. Cyclic data
206structures cannot be encoded in this mode.
202 207
203This option does not affect C<decode> in any way - shared values and 208This option does not affect C<decode> in any way - shared values and
204references will always be decoded properly if present. It is recommended 209references will always be decoded properly if present.
205to leave it off unless you know your communications partner supports the 210
206value sharing extensions to CBOR (http://cbor.schmorp.de/value-sharing). 211=item $cbor = $cbor->allow_cycles ([$enable])
212
213=item $enabled = $cbor->get_allow_cycles
214
215If C<$enable> is true (or missing), then C<decode> will happily decode
216self-referential (cyclic) data structures. By default these will not be
217decoded, as they need manual cleanup to avoid memory leaks, so code that
218isn't prepared for this will not leak memory.
219
220If C<$enable> is false (the default), then C<decode> will throw an error
221when it encounters a self-referential/cyclic data structure.
222
223This option does not affect C<encode> in any way - shared values and
224references will always be decoded properly if present.
225
226=item $cbor = $cbor->pack_strings ([$enable])
227
228=item $enabled = $cbor->get_pack_strings
229
230If C<$enable> is true (or missing), then C<encode> will try not to encode
231the same string twice, but will instead encode a reference to the string
232instead. Depending on your data format, this can save a lot of space, but
233also results in a very large runtime overhead (expect encoding times to be
2342-4 times as high as without).
235
236It is recommended to leave it off unless you know your
237communications partner supports the stringref extension to CBOR
238(L<http://cbor.schmorp.de/stringref>), as without decoder support, the
239resulting data structure might not be usable.
240
241If C<$enable> is false (the default), then C<encode> will encode strings
242the standard CBOR way.
243
244This option does not affect C<decode> in any way - string references will
245always be decoded properly if present.
246
247=item $cbor = $cbor->filter ([$cb->($tag, $value)])
248
249=item $cb_or_undef = $cbor->get_filter
250
251Sets or replaces the tagged value decoding filter (when C<$cb> is
252specified) or clears the filter (if no argument or C<undef> is provided).
253
254The filter callback is called only during decoding, when a non-enforced
255tagged value has been decoded (see L<TAG HANDLING AND EXTENSIONS> for a
256list of enforced tags). For specific tags, it's often better to provide a
257default converter using the C<%CBOR::XS::FILTER> hash (see below).
258
259The first argument is the numerical tag, the second is the (decoded) value
260that has been tagged.
261
262The filter function should return either exactly one value, which will
263replace the tagged value in the decoded data structure, or no values,
264which will result in default handling, which currently means the decoder
265creates a C<CBOR::XS::Tagged> object to hold the tag and the value.
266
267When the filter is cleared (the default state), the default filter
268function, C<CBOR::XS::default_filter>, is used. This function simply looks
269up the tag in the C<%CBOR::XS::FILTER> hash. If an entry exists it must be
270a code reference that is called with tag and value, and is responsible for
271decoding the value. If no entry exists, it returns no values.
272
273Example: decode all tags not handled internally into C<CBOR::XS::Tagged>
274objects, with no other special handling (useful when working with
275potentially "unsafe" CBOR data).
276
277 CBOR::XS->new->filter (sub { })->decode ($cbor_data);
278
279Example: provide a global filter for tag 1347375694, converting the value
280into some string form.
281
282 $CBOR::XS::FILTER{1347375694} = sub {
283 my ($tag, $value);
284
285 "tag 1347375694 value $value"
286 };
207 287
208=item $cbor_data = $cbor->encode ($perl_scalar) 288=item $cbor_data = $cbor->encode ($perl_scalar)
209 289
210Converts the given Perl data structure (a scalar value) to its CBOR 290Converts the given Perl data structure (a scalar value) to its CBOR
211representation. 291representation.
252CBOR integers become (numeric) perl scalars. On perls without 64 bit 332CBOR integers become (numeric) perl scalars. On perls without 64 bit
253support, 64 bit integers will be truncated or otherwise corrupted. 333support, 64 bit integers will be truncated or otherwise corrupted.
254 334
255=item byte strings 335=item byte strings
256 336
257Byte strings will become octet strings in Perl (the byte values 0..255 337Byte strings will become octet strings in Perl (the Byte values 0..255
258will simply become characters of the same value in Perl). 338will simply become characters of the same value in Perl).
259 339
260=item UTF-8 strings 340=item UTF-8 strings
261 341
262UTF-8 strings in CBOR will be decoded, i.e. the UTF-8 octets will be 342UTF-8 strings in CBOR will be decoded, i.e. the UTF-8 octets will be
280C<Types:Serialiser::false> and C<Types::Serialiser::error>, 360C<Types:Serialiser::false> and C<Types::Serialiser::error>,
281respectively. They are overloaded to act almost exactly like the numbers 361respectively. They are overloaded to act almost exactly like the numbers
282C<1> and C<0> (for true and false) or to throw an exception on access (for 362C<1> and C<0> (for true and false) or to throw an exception on access (for
283error). See the L<Types::Serialiser> manpage for details. 363error). See the L<Types::Serialiser> manpage for details.
284 364
285=item CBOR tag 256 (perl object) 365=item tagged values
286 366
287The tag value C<256> (TODO: pending iana registration) will be used
288to deserialise a Perl object serialised with C<FREEZE>. See L<OBJECT
289SERIALISATION>, below, for details.
290
291=item CBOR tag 55799 (magic header)
292
293The tag 55799 is ignored (this tag implements the magic header).
294
295=item other CBOR tags
296
297Tagged items consists of a numeric tag and another CBOR value. Tags not 367Tagged items consists of a numeric tag and another CBOR value.
298handled internally are currently converted into a L<CBOR::XS::Tagged>
299object, which is simply a blessed array reference consisting of the
300numeric tag value followed by the (decoded) CBOR value.
301 368
302In the future, support for user-supplied conversions might get added. 369See L<TAG HANDLING AND EXTENSIONS> and the description of C<< ->filter >>
370for details on which tags are handled how.
303 371
304=item anything else 372=item anything else
305 373
306Anything else (e.g. unsupported simple values) will raise a decoding 374Anything else (e.g. unsupported simple values) will raise a decoding
307error. 375error.
310 378
311 379
312=head2 PERL -> CBOR 380=head2 PERL -> CBOR
313 381
314The mapping from Perl to CBOR is slightly more difficult, as Perl is a 382The mapping from Perl to CBOR is slightly more difficult, as Perl is a
315truly typeless language, so we can only guess which CBOR type is meant by 383typeless language. That means this module can only guess which CBOR type
316a Perl value. 384is meant by a perl value.
317 385
318=over 4 386=over 4
319 387
320=item hash references 388=item hash references
321 389
322Perl hash references become CBOR maps. As there is no inherent ordering in 390Perl hash references become CBOR maps. As there is no inherent ordering in
323hash keys (or CBOR maps), they will usually be encoded in a pseudo-random 391hash keys (or CBOR maps), they will usually be encoded in a pseudo-random
324order. 392order. This order can be different each time a hahs is encoded.
325 393
326Currently, tied hashes will use the indefinite-length format, while normal 394Currently, tied hashes will use the indefinite-length format, while normal
327hashes will use the fixed-length format. 395hashes will use the fixed-length format.
328 396
329=item array references 397=item array references
330 398
331Perl array references become fixed-length CBOR arrays. 399Perl array references become fixed-length CBOR arrays.
332 400
333=item other references 401=item other references
334 402
335Other unblessed references are generally not allowed and will cause an 403Other unblessed references will be represented using
336exception to be thrown, except for references to the integers C<0> and 404the indirection tag extension (tag value C<22098>,
337C<1>, which get turned into false and true in CBOR. 405L<http://cbor.schmorp.de/indirection>). CBOR decoders are guaranteed
406to be able to decode these values somehow, by either "doing the right
407thing", decoding into a generic tagged object, simply ignoring the tag, or
408something else.
338 409
339=item CBOR::XS::Tagged objects 410=item CBOR::XS::Tagged objects
340 411
341Objects of this type must be arrays consisting of a single C<[tag, value]> 412Objects of this type must be arrays consisting of a single C<[tag, value]>
342pair. The (numerical) tag will be encoded as a CBOR tag, the value will 413pair. The (numerical) tag will be encoded as a CBOR tag, the value will
343be encoded as appropriate for the value. You cna use C<CBOR::XS::tag> to 414be encoded as appropriate for the value. You must use C<CBOR::XS::tag> to
344create such objects. 415create such objects.
345 416
346=item Types::Serialiser::true, Types::Serialiser::false, Types::Serialiser::error 417=item Types::Serialiser::true, Types::Serialiser::false, Types::Serialiser::error
347 418
348These special values become CBOR true, CBOR false and CBOR undefined 419These special values become CBOR true, CBOR false and CBOR undefined
350if you want. 421if you want.
351 422
352=item other blessed objects 423=item other blessed objects
353 424
354Other blessed objects are serialised via C<TO_CBOR> or C<FREEZE>. See 425Other blessed objects are serialised via C<TO_CBOR> or C<FREEZE>. See
355L<OBJECT SERIALISATION>, below, for details. 426L<TAG HANDLING AND EXTENSIONS> for specific classes handled by this
427module, and L<OBJECT SERIALISATION> for generic object serialisation.
356 428
357=item simple scalars 429=item simple scalars
358 430
359TODO
360Simple Perl scalars (any scalar that is not a reference) are the most 431Simple Perl scalars (any scalar that is not a reference) are the most
361difficult objects to encode: CBOR::XS will encode undefined scalars as 432difficult objects to encode: CBOR::XS will encode undefined scalars as
362CBOR null values, scalars that have last been used in a string context 433CBOR null values, scalars that have last been used in a string context
363before encoding as CBOR strings, and anything else as number value: 434before encoding as CBOR strings, and anything else as number value:
364 435
365 # dump as number 436 # dump as number
366 encode_cbor [2] # yields [2] 437 encode_cbor [2] # yields [2]
367 encode_cbor [-3.0e17] # yields [-3e+17] 438 encode_cbor [-3.0e17] # yields [-3e+17]
368 my $value = 5; encode_cbor [$value] # yields [5] 439 my $value = 5; encode_cbor [$value] # yields [5]
369 440
370 # used as string, so dump as string 441 # used as string, so dump as string (either byte or text)
371 print $value; 442 print $value;
372 encode_cbor [$value] # yields ["5"] 443 encode_cbor [$value] # yields ["5"]
373 444
374 # undef becomes null 445 # undef becomes null
375 encode_cbor [undef] # yields [null] 446 encode_cbor [undef] # yields [null]
378 449
379 my $x = 3.1; # some variable containing a number 450 my $x = 3.1; # some variable containing a number
380 "$x"; # stringified 451 "$x"; # stringified
381 $x .= ""; # another, more awkward way to stringify 452 $x .= ""; # another, more awkward way to stringify
382 print $x; # perl does it for you, too, quite often 453 print $x; # perl does it for you, too, quite often
454
455You can force whether a string ie encoded as byte or text string by using
456C<utf8::upgrade> and C<utf8::downgrade>):
457
458 utf8::upgrade $x; # encode $x as text string
459 utf8::downgrade $x; # encode $x as byte string
460
461Perl doesn't define what operations up- and downgrade strings, so if the
462difference between byte and text is important, you should up- or downgrade
463your string as late as possible before encoding.
383 464
384You can force the type to be a CBOR number by numifying it: 465You can force the type to be a CBOR number by numifying it:
385 466
386 my $x = "3"; # some variable containing a string 467 my $x = "3"; # some variable containing a string
387 $x += 0; # numify it, ensuring it will be dumped as a number 468 $x += 0; # numify it, ensuring it will be dumped as a number
400 481
401=back 482=back
402 483
403=head2 OBJECT SERIALISATION 484=head2 OBJECT SERIALISATION
404 485
486This module implements both a CBOR-specific and the generic
487L<Types::Serialier> object serialisation protocol. The following
488subsections explain both methods.
489
490=head3 ENCODING
491
405This module knows two way to serialise a Perl object: The CBOR-specific 492This module knows two way to serialise a Perl object: The CBOR-specific
406way, and the generic way. 493way, and the generic way.
407 494
408Whenever the encoder encounters a Perl object that it cnanot serialise 495Whenever the encoder encounters a Perl object that it cannot serialise
409directly (most of them), it will first look up the C<TO_CBOR> method on 496directly (most of them), it will first look up the C<TO_CBOR> method on
410it. 497it.
411 498
412If it has a C<TO_CBOR> method, it will call it with the object as only 499If it has a C<TO_CBOR> method, it will call it with the object as only
413argument, and expects exactly one return value, which it will then 500argument, and expects exactly one return value, which it will then
419 506
420The C<FREEZE> method can return any number of values (i.e. zero or 507The C<FREEZE> method can return any number of values (i.e. zero or
421more). These will be encoded as CBOR perl object, together with the 508more). These will be encoded as CBOR perl object, together with the
422classname. 509classname.
423 510
511These methods I<MUST NOT> change the data structure that is being
512serialised. Failure to comply to this can result in memory corruption -
513and worse.
514
424If an object supports neither C<TO_CBOR> nor C<FREEZE>, encoding will fail 515If an object supports neither C<TO_CBOR> nor C<FREEZE>, encoding will fail
425with an error. 516with an error.
426 517
518=head3 DECODING
519
427Objects encoded via C<TO_CBOR> cannot be automatically decoded, but 520Objects encoded via C<TO_CBOR> cannot (normally) be automatically decoded,
428objects encoded via C<FREEZE> can be decoded using the following protocol: 521but objects encoded via C<FREEZE> can be decoded using the following
522protocol:
429 523
430When an encoded CBOR perl object is encountered by the decoder, it will 524When an encoded CBOR perl object is encountered by the decoder, it will
431look up the C<THAW> method, by using the stored classname, and will fail 525look up the C<THAW> method, by using the stored classname, and will fail
432if the method cannot be found. 526if the method cannot be found.
433 527
434After the lookup it will call the C<THAW> method with the stored classname 528After the lookup it will call the C<THAW> method with the stored classname
435as first argument, the constant string C<CBOR> as second argument, and all 529as first argument, the constant string C<CBOR> as second argument, and all
436values returned by C<FREEZE> as remaining arguments. 530values returned by C<FREEZE> as remaining arguments.
437 531
438=head4 EXAMPLES 532=head3 EXAMPLES
439 533
440Here is an example C<TO_CBOR> method: 534Here is an example C<TO_CBOR> method:
441 535
442 sub My::Object::TO_CBOR { 536 sub My::Object::TO_CBOR {
443 my ($obj) = @_; 537 my ($obj) = @_;
454 548
455 sub URI::TO_CBOR { 549 sub URI::TO_CBOR {
456 my ($self) = @_; 550 my ($self) = @_;
457 my $uri = "$self"; # stringify uri 551 my $uri = "$self"; # stringify uri
458 utf8::upgrade $uri; # make sure it will be encoded as UTF-8 string 552 utf8::upgrade $uri; # make sure it will be encoded as UTF-8 string
459 CBOR::XS::tagged 32, "$_[0]" 553 CBOR::XS::tag 32, "$_[0]"
460 } 554 }
461 555
462This will encode URIs as a UTF-8 string with tag 32, which indicates an 556This will encode URIs as a UTF-8 string with tag 32, which indicates an
463URI. 557URI.
464 558
600 CBOR::XS::tag 24, 694 CBOR::XS::tag 24,
601 encode_cbor [1, 2, 3]; 695 encode_cbor [1, 2, 3];
602 696
603=head1 TAG HANDLING AND EXTENSIONS 697=head1 TAG HANDLING AND EXTENSIONS
604 698
605This section describes how this module handles specific tagged values and 699This section describes how this module handles specific tagged values
606extensions. If a tag is not mentioned here, then the default handling 700and extensions. If a tag is not mentioned here and no additional filters
701are provided for it, then the default handling applies (creating a
607applies (creating a CBOR::XS::Tagged object on decoding, and only encoding 702CBOR::XS::Tagged object on decoding, and only encoding the tag when
608the tag when explicitly requested). 703explicitly requested).
704
705Tags not handled specifically are currently converted into a
706L<CBOR::XS::Tagged> object, which is simply a blessed array reference
707consisting of the numeric tag value followed by the (decoded) CBOR value.
609 708
610Future versions of this module reserve the right to special case 709Future versions of this module reserve the right to special case
611additional tags (such as bigfloat or base64url). 710additional tags (such as base64url).
711
712=head2 ENFORCED TAGS
713
714These tags are always handled when decoding, and their handling cannot be
715overriden by the user.
612 716
613=over 4 717=over 4
614 718
615=item <unassigned> (perl-object, L<http://cbor.schmorp.de/perl-object>) 719=item 26 (perl-object, L<http://cbor.schmorp.de/perl-object>)
616 720
617These tags are automatically created for serialisable objects using the 721These tags are automatically created (and decoded) for serialisable
618C<FREEZE/THAW> methods (the L<Types::Serialier> object serialisation 722objects using the C<FREEZE/THAW> methods (the L<Types::Serialier> object
619protocol). 723serialisation protocol). See L<OBJECT SERIALISATION> for details.
620 724
621=item <unassigned>, <unassigned> (sharable, sharedref, L <http://cbor.schmorp.de/value-sharing>) 725=item 28, 29 (shareable, sharedref, L <http://cbor.schmorp.de/value-sharing>)
622 726
623These tags are automatically decoded when encountered, resulting in 727These tags are automatically decoded when encountered (and they do not
728result in a cyclic data structure, see C<allow_cycles>), resulting in
624shared values in the decoded object. They are only encoded, however, when 729shared values in the decoded object. They are only encoded, however, when
625C<allow_sharable> is enabled. 730C<allow_sharing> is enabled.
731
732Not all shared values can be successfully decoded: values that reference
733themselves will I<currently> decode as C<undef> (this is not the same
734as a reference pointing to itself, which will be represented as a value
735that contains an indirect reference to itself - these will be decoded
736properly).
737
738Note that considerably more shared value data structures can be decoded
739than will be encoded - currently, only values pointed to by references
740will be shared, others will not. While non-reference shared values can be
741generated in Perl with some effort, they were considered too unimportant
742to be supported in the encoder. The decoder, however, will decode these
743values as shared values.
744
745=item 256, 25 (stringref-namespace, stringref, L <http://cbor.schmorp.de/stringref>)
746
747These tags are automatically decoded when encountered. They are only
748encoded, however, when C<pack_strings> is enabled.
626 749
627=item 22098 (indirection, L<http://cbor.schmorp.de/indirection>) 750=item 22098 (indirection, L<http://cbor.schmorp.de/indirection>)
628 751
629This tag is automatically generated when a reference are encountered (with 752This tag is automatically generated when a reference are encountered (with
630the exception of hash and array refernces). It is converted to a reference 753the exception of hash and array refernces). It is converted to a reference
634 757
635This value is not generated on encoding (unless explicitly requested by 758This value is not generated on encoding (unless explicitly requested by
636the user), and is simply ignored when decoding. 759the user), and is simply ignored when decoding.
637 760
638=back 761=back
762
763=head2 NON-ENFORCED TAGS
764
765These tags have default filters provided when decoding. Their handling can
766be overriden by changing the C<%CBOR::XS::FILTER> entry for the tag, or by
767providing a custom C<filter> callback when decoding.
768
769When they result in decoding into a specific Perl class, the module
770usually provides a corresponding C<TO_CBOR> method as well.
771
772When any of these need to load additional modules that are not part of the
773perl core distribution (e.g. L<URI>), it is (currently) up to the user to
774provide these modules. The decoding usually fails with an exception if the
775required module cannot be loaded.
776
777=over 4
778
779=item 2, 3 (positive/negative bignum)
780
781These tags are decoded into L<Math::BigInt> objects. The corresponding
782C<Math::BigInt::TO_CBOR> method encodes "small" bigints into normal CBOR
783integers, and others into positive/negative CBOR bignums.
784
785=item 4, 5 (decimal fraction/bigfloat)
786
787Both decimal fractions and bigfloats are decoded into L<Math::BigFloat>
788objects. The corresponding C<Math::BigFloat::TO_CBOR> method I<always>
789encodes into a decimal fraction.
790
791CBOR cannot represent bigfloats with I<very> large exponents - conversion
792of such big float objects is undefined.
793
794Also, NaN and infinities are not encoded properly.
795
796=item 21, 22, 23 (expected later JSON conversion)
797
798CBOR::XS is not a CBOR-to-JSON converter, and will simply ignore these
799tags.
800
801=item 32 (URI)
802
803These objects decode into L<URI> objects. The corresponding
804C<URI::TO_CBOR> method again results in a CBOR URI value.
805
806=back
807
808=cut
809
810our %FILTER = (
811 # 0 # rfc4287 datetime, utf-8
812 # 1 # unix timestamp, any
813
814 2 => sub { # pos bigint
815 require Math::BigInt;
816 Math::BigInt->new ("0x" . unpack "H*", pop)
817 },
818
819 3 => sub { # neg bigint
820 require Math::BigInt;
821 -Math::BigInt->new ("0x" . unpack "H*", pop)
822 },
823
824 4 => sub { # decimal fraction, array
825 require Math::BigFloat;
826 Math::BigFloat->new ($_[1][1] . "E" . $_[1][0])
827 },
828
829 5 => sub { # bigfloat, array
830 require Math::BigFloat;
831 scalar Math::BigFloat->new ($_[1][1])->blsft ($_[1][0], 2)
832 },
833
834 21 => sub { pop }, # expected conversion to base64url encoding
835 22 => sub { pop }, # expected conversion to base64 encoding
836 23 => sub { pop }, # expected conversion to base16 encoding
837
838 # 24 # embedded cbor, byte string
839
840 32 => sub {
841 require URI;
842 URI->new (pop)
843 },
844
845 # 33 # base64url rfc4648, utf-8
846 # 34 # base64 rfc46484, utf-8
847 # 35 # regex pcre/ecma262, utf-8
848 # 36 # mime message rfc2045, utf-8
849);
639 850
640 851
641=head1 CBOR and JSON 852=head1 CBOR and JSON
642 853
643CBOR is supposed to implement a superset of the JSON data model, and is, 854CBOR is supposed to implement a superset of the JSON data model, and is,
705properly. Half precision types are accepted, but not encoded. 916properly. Half precision types are accepted, but not encoded.
706 917
707Strict mode and canonical mode are not implemented. 918Strict mode and canonical mode are not implemented.
708 919
709 920
921=head1 LIMITATIONS ON PERLS WITHOUT 64-BIT INTEGER SUPPORT
922
923On perls that were built without 64 bit integer support (these are rare
924nowadays, even on 32 bit architectures), support for any kind of 64 bit
925integer in CBOR is very limited - most likely, these 64 bit values will
926be truncated, corrupted, or otherwise not decoded correctly. This also
927includes string, array and map sizes that are stored as 64 bit integers.
928
929
710=head1 THREADS 930=head1 THREADS
711 931
712This module is I<not> guaranteed to be thread safe and there are no 932This module is I<not> guaranteed to be thread safe and there are no
713plans to change this until Perl gets thread support (as opposed to the 933plans to change this until Perl gets thread support (as opposed to the
714horribly slow so-called "threads" which are simply slow and bloated 934horribly slow so-called "threads" which are simply slow and bloated
726Please refrain from using rt.cpan.org or any other bug reporting 946Please refrain from using rt.cpan.org or any other bug reporting
727service. I put the contact address into my modules for a reason. 947service. I put the contact address into my modules for a reason.
728 948
729=cut 949=cut
730 950
951our %FILTER = (
952 # 0 # rfc4287 datetime, utf-8
953 # 1 # unix timestamp, any
954
955 2 => sub { # pos bigint
956 require Math::BigInt;
957 Math::BigInt->new ("0x" . unpack "H*", pop)
958 },
959
960 3 => sub { # neg bigint
961 require Math::BigInt;
962 -Math::BigInt->new ("0x" . unpack "H*", pop)
963 },
964
965 4 => sub { # decimal fraction, array
966 require Math::BigFloat;
967 Math::BigFloat->new ($_[1][1] . "E" . $_[1][0])
968 },
969
970 5 => sub { # bigfloat, array
971 require Math::BigFloat;
972 scalar Math::BigFloat->new ($_[1][1])->blsft ($_[1][0], 2)
973 },
974
975 21 => sub { pop }, # expected conversion to base64url encoding
976 22 => sub { pop }, # expected conversion to base64 encoding
977 23 => sub { pop }, # expected conversion to base16 encoding
978
979 # 24 # embedded cbor, byte string
980
981 32 => sub {
982 require URI;
983 URI->new (pop)
984 },
985
986 # 33 # base64url rfc4648, utf-8
987 # 34 # base64 rfc46484, utf-8
988 # 35 # regex pcre/ecma262, utf-8
989 # 36 # mime message rfc2045, utf-8
990);
991
992sub CBOR::XS::default_filter {
993 &{ $FILTER{$_[0]} or return }
994}
995
996sub URI::TO_CBOR {
997 my $uri = $_[0]->as_string;
998 utf8::upgrade $uri;
999 CBOR::XS::tag 32, $uri
1000}
1001
1002sub Math::BigInt::TO_CBOR {
1003 if ($_[0] >= -2147483648 && $_[0] <= 2147483647) {
1004 $_[0]->numify
1005 } else {
1006 my $hex = substr $_[0]->as_hex, 2;
1007 $hex = "0$hex" if 1 & length $hex; # sigh
1008 CBOR::XS::tag $_[0] >= 0 ? 2 : 3, pack "H*", $hex
1009 }
1010}
1011
1012sub Math::BigFloat::TO_CBOR {
1013 my ($m, $e) = $_[0]->parts;
1014 CBOR::XS::tag 4, [$e->numify, $m]
1015}
1016
731XSLoader::load "CBOR::XS", $VERSION; 1017XSLoader::load "CBOR::XS", $VERSION;
732 1018
733=head1 SEE ALSO 1019=head1 SEE ALSO
734 1020
735The L<JSON> and L<JSON::XS> modules that do similar, but human-readable, 1021The L<JSON> and L<JSON::XS> modules that do similar, but human-readable,

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines