… | |
… | |
46 | In short, CBOR is a faster and very compact binary alternative to JSON, |
46 | In short, CBOR is a faster and very compact binary alternative to JSON, |
47 | with the added ability of supporting serialisation of Perl objects. (JSON |
47 | with the added ability of supporting serialisation of Perl objects. (JSON |
48 | often compresses better than CBOR though, so if you plan to compress the |
48 | often compresses better than CBOR though, so if you plan to compress the |
49 | data later you might want to compare both formats first). |
49 | data later you might want to compare both formats first). |
50 | |
50 | |
|
|
51 | To give you a general idea about speed, with texts in the megabyte range, |
|
|
52 | C<CBOR::XS> usually encodes roughly twice as fast as L<Storable> or |
|
|
53 | L<JSON::XS> and decodes about 15%-30% faster than those. The shorter the |
|
|
54 | data, the worse L<Storable> performs in comparison. |
|
|
55 | |
|
|
56 | As for compactness, C<CBOR::XS> encoded data structures are usually about |
|
|
57 | 20% smaller than the same data encoded as (compact) JSON or L<Storable>. |
|
|
58 | |
51 | The primary goal of this module is to be I<correct> and the secondary goal |
59 | The primary goal of this module is to be I<correct> and the secondary goal |
52 | is to be I<fast>. To reach the latter goal it was written in C. |
60 | is to be I<fast>. To reach the latter goal it was written in C. |
53 | |
61 | |
54 | See MAPPING, below, on how CBOR::XS maps perl values to CBOR values and |
62 | See MAPPING, below, on how CBOR::XS maps perl values to CBOR values and |
55 | vice versa. |
63 | vice versa. |
… | |
… | |
58 | |
66 | |
59 | package CBOR::XS; |
67 | package CBOR::XS; |
60 | |
68 | |
61 | use common::sense; |
69 | use common::sense; |
62 | |
70 | |
63 | our $VERSION = 0.05; |
71 | our $VERSION = 0.06; |
64 | our @ISA = qw(Exporter); |
72 | our @ISA = qw(Exporter); |
65 | |
73 | |
66 | our @EXPORT = qw(encode_cbor decode_cbor); |
74 | our @EXPORT = qw(encode_cbor decode_cbor); |
67 | |
75 | |
68 | use Exporter; |
76 | use Exporter; |
… | |
… | |
283 | C<1>, which get turned into false and true in CBOR. |
291 | C<1>, which get turned into false and true in CBOR. |
284 | |
292 | |
285 | =item CBOR::XS::Tagged objects |
293 | =item CBOR::XS::Tagged objects |
286 | |
294 | |
287 | Objects of this type must be arrays consisting of a single C<[tag, value]> |
295 | Objects of this type must be arrays consisting of a single C<[tag, value]> |
288 | pair. The (numerical) tag will be encoded as a CBOR tag, the value will be |
296 | pair. The (numerical) tag will be encoded as a CBOR tag, the value will |
289 | encoded as appropriate for the value. |
297 | be encoded as appropriate for the value. You cna use C<CBOR::XS::tag> to |
|
|
298 | create such objects. |
290 | |
299 | |
291 | =item Types::Serialiser::true, Types::Serialiser::false, Types::Serialiser::error |
300 | =item Types::Serialiser::true, Types::Serialiser::false, Types::Serialiser::error |
292 | |
301 | |
293 | These special values become CBOR true, CBOR false and CBOR undefined |
302 | These special values become CBOR true, CBOR false and CBOR undefined |
294 | values, respectively. You can also use C<\1>, C<\0> and C<\undef> directly |
303 | values, respectively. You can also use C<\1>, C<\0> and C<\undef> directly |
… | |
… | |
453 | This string is available as C<$CBOR::XS::MAGIC>. This module does not |
462 | This string is available as C<$CBOR::XS::MAGIC>. This module does not |
454 | prepend this string tot he CBOR data it generates, but it will ignroe it |
463 | prepend this string tot he CBOR data it generates, but it will ignroe it |
455 | if present, so users can prepend this string as a "file type" indicator as |
464 | if present, so users can prepend this string as a "file type" indicator as |
456 | required. |
465 | required. |
457 | |
466 | |
|
|
467 | |
|
|
468 | =head1 THE CBOR::XS::Tagged CLASS |
|
|
469 | |
|
|
470 | CBOR has the concept of tagged values - any CBOR value can be tagged with |
|
|
471 | a numeric 64 bit number, which are centrally administered. |
|
|
472 | |
|
|
473 | C<CBOR::XS> handles a few tags internally when en- or decoding. You can |
|
|
474 | also create tags yourself by encoding C<CBOR::XS::Tagged> objects, and the |
|
|
475 | decoder will create C<CBOR::XS::Tagged> objects itself when it hits an |
|
|
476 | unknown tag. |
|
|
477 | |
|
|
478 | These objects are simply blessed array references - the first member of |
|
|
479 | the array being the numerical tag, the second being the value. |
|
|
480 | |
|
|
481 | You can interact with C<CBOR::XS::Tagged> objects in the following ways: |
|
|
482 | |
|
|
483 | =over 4 |
|
|
484 | |
|
|
485 | =item $tagged = CBOR::XS::tag $tag, $value |
|
|
486 | |
|
|
487 | This function(!) creates a new C<CBOR::XS::Tagged> object using the given |
|
|
488 | C<$tag> (0..2**64-1) to tag the given C<$value> (which can be any Perl |
|
|
489 | value that can be encoded in CBOR, including serialisable Perl objects and |
|
|
490 | C<CBOR::XS::Tagged> objects). |
|
|
491 | |
|
|
492 | =item $tagged->[0] |
|
|
493 | |
|
|
494 | =item $tagged->[0] = $new_tag |
|
|
495 | |
|
|
496 | =item $tag = $tagged->tag |
|
|
497 | |
|
|
498 | =item $new_tag = $tagged->tag ($new_tag) |
|
|
499 | |
|
|
500 | Access/mutate the tag. |
|
|
501 | |
|
|
502 | =item $tagged->[1] |
|
|
503 | |
|
|
504 | =item $tagged->[1] = $new_value |
|
|
505 | |
|
|
506 | =item $value = $tagged->value |
|
|
507 | |
|
|
508 | =item $new_value = $tagged->value ($new_value) |
|
|
509 | |
|
|
510 | Access/mutate the tagged value. |
|
|
511 | |
|
|
512 | =back |
|
|
513 | |
|
|
514 | =cut |
|
|
515 | |
|
|
516 | sub tag($$) { |
|
|
517 | bless [@_], CBOR::XS::Tagged::; |
|
|
518 | } |
|
|
519 | |
|
|
520 | sub CBOR::XS::Tagged::tag { |
|
|
521 | $_[0][0] = $_[1] if $#_; |
|
|
522 | $_[0][0] |
|
|
523 | } |
|
|
524 | |
|
|
525 | sub CBOR::XS::Tagged::value { |
|
|
526 | $_[0][1] = $_[1] if $#_; |
|
|
527 | $_[0][1] |
|
|
528 | } |
|
|
529 | |
|
|
530 | =head2 EXAMPLES |
|
|
531 | |
|
|
532 | Here are some examples of C<CBOR::XS::Tagged> uses to tag objects. |
|
|
533 | |
|
|
534 | You can look up CBOR tag value and emanings in the IANA registry at |
|
|
535 | L<http://www.iana.org/assignments/cbor-tags/cbor-tags.xhtml>. |
|
|
536 | |
|
|
537 | Prepend a magic header (C<$CBOR::XS::MAGIC>): |
|
|
538 | |
|
|
539 | my $cbor = encode_cbor CBOR::XS::tag 55799, $value; |
|
|
540 | # same as: |
|
|
541 | my $cbor = $CBOR::XS::MAGIC . encode_cbor $value; |
|
|
542 | |
|
|
543 | Serialise some URIs and a regex in an array: |
|
|
544 | |
|
|
545 | my $cbor = encode_cbor [ |
|
|
546 | (CBOR::XS::tag 32, "http://www.nethype.de/"), |
|
|
547 | (CBOR::XS::tag 32, "http://software.schmorp.de/"), |
|
|
548 | (CBOR::XS::tag 35, "^[Pp][Ee][Rr][lL]\$"), |
|
|
549 | ]; |
|
|
550 | |
|
|
551 | Wrap CBOR data in CBOR: |
|
|
552 | |
|
|
553 | my $cbor_cbor = encode_cbor |
|
|
554 | CBOR::XS::tag 24, |
|
|
555 | encode_cbor [1, 2, 3]; |
458 | |
556 | |
459 | =head1 CBOR and JSON |
557 | =head1 CBOR and JSON |
460 | |
558 | |
461 | CBOR is supposed to implement a superset of the JSON data model, and is, |
559 | CBOR is supposed to implement a superset of the JSON data model, and is, |
462 | with some coercion, able to represent all JSON texts (something that other |
560 | with some coercion, able to represent all JSON texts (something that other |