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.11 by root, Tue Oct 29 00:20:26 2013 UTC vs.
Revision 1.16 by root, Tue Oct 29 22:04:52 2013 UTC

46In short, CBOR is a faster and very compact binary alternative to JSON, 46In short, CBOR is a faster and very compact binary alternative to JSON,
47with the added ability of supporting serialisation of Perl objects. (JSON 47with the added ability of supporting serialisation of Perl objects. (JSON
48often compresses better than CBOR though, so if you plan to compress the 48often compresses better than CBOR though, so if you plan to compress the
49data later you might want to compare both formats first). 49data later you might want to compare both formats first).
50 50
51To 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
53L<JSON::XS> and decodes about 15%-30% faster than those. The shorter the
54data, the worse L<Storable> performs in comparison.
55
56As for compactness, C<CBOR::XS> encoded data structures are usually about
5720% smaller than the same data encoded as (compact) JSON or L<Storable>.
58
51The primary goal of this module is to be I<correct> and the secondary goal 59The primary goal of this module is to be I<correct> and the secondary goal
52is to be I<fast>. To reach the latter goal it was written in C. 60is to be I<fast>. To reach the latter goal it was written in C.
53 61
54See MAPPING, below, on how CBOR::XS maps perl values to CBOR values and 62See MAPPING, below, on how CBOR::XS maps perl values to CBOR values and
55vice versa. 63vice versa.
58 66
59package CBOR::XS; 67package CBOR::XS;
60 68
61use common::sense; 69use common::sense;
62 70
63our $VERSION = 0.05; 71our $VERSION = 0.07;
64our @ISA = qw(Exporter); 72our @ISA = qw(Exporter);
65 73
66our @EXPORT = qw(encode_cbor decode_cbor); 74our @EXPORT = qw(encode_cbor decode_cbor);
67 75
68use Exporter; 76use Exporter;
283C<1>, which get turned into false and true in CBOR. 291C<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
287Objects of this type must be arrays consisting of a single C<[tag, value]> 295Objects of this type must be arrays consisting of a single C<[tag, value]>
288pair. The (numerical) tag will be encoded as a CBOR tag, the value will be 296pair. The (numerical) tag will be encoded as a CBOR tag, the value will
289encoded as appropriate for the value. 297be encoded as appropriate for the value. You cna use C<CBOR::XS::tag> to
298create 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
293These special values become CBOR true, CBOR false and CBOR undefined 302These special values become CBOR true, CBOR false and CBOR undefined
294values, respectively. You can also use C<\1>, C<\0> and C<\undef> directly 303values, respectively. You can also use C<\1>, C<\0> and C<\undef> directly
453This string is available as C<$CBOR::XS::MAGIC>. This module does not 462This string is available as C<$CBOR::XS::MAGIC>. This module does not
454prepend this string tot he CBOR data it generates, but it will ignroe it 463prepend this string tot he CBOR data it generates, but it will ignroe it
455if present, so users can prepend this string as a "file type" indicator as 464if present, so users can prepend this string as a "file type" indicator as
456required. 465required.
457 466
467
468=head1 THE CBOR::XS::Tagged CLASS
469
470CBOR has the concept of tagged values - any CBOR value can be tagged with
471a numeric 64 bit number, which are centrally administered.
472
473C<CBOR::XS> handles a few tags internally when en- or decoding. You can
474also create tags yourself by encoding C<CBOR::XS::Tagged> objects, and the
475decoder will create C<CBOR::XS::Tagged> objects itself when it hits an
476unknown tag.
477
478These objects are simply blessed array references - the first member of
479the array being the numerical tag, the second being the value.
480
481You 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
487This function(!) creates a new C<CBOR::XS::Tagged> object using the given
488C<$tag> (0..2**64-1) to tag the given C<$value> (which can be any Perl
489value that can be encoded in CBOR, including serialisable Perl objects and
490C<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
500Access/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
510Access/mutate the tagged value.
511
512=back
513
514=cut
515
516sub tag($$) {
517 bless [@_], CBOR::XS::Tagged::;
518}
519
520sub CBOR::XS::Tagged::tag {
521 $_[0][0] = $_[1] if $#_;
522 $_[0][0]
523}
524
525sub CBOR::XS::Tagged::value {
526 $_[0][1] = $_[1] if $#_;
527 $_[0][1]
528}
529
530=head2 EXAMPLES
531
532Here are some examples of C<CBOR::XS::Tagged> uses to tag objects.
533
534You can look up CBOR tag value and emanings in the IANA registry at
535L<http://www.iana.org/assignments/cbor-tags/cbor-tags.xhtml>.
536
537Prepend 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
543Serialise 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
551Wrap 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
461CBOR is supposed to implement a superset of the JSON data model, and is, 559CBOR is supposed to implement a superset of the JSON data model, and is,
462with some coercion, able to represent all JSON texts (something that other 560with some coercion, able to represent all JSON texts (something that other

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines