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.27 by root, Thu Nov 28 15:43:24 2013 UTC vs.
Revision 1.28 by root, Thu Nov 28 16:09:04 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
32to you to do). Furthermore, details of the implementation might change
33freely before version 1.0. And lastly, most extensions depend on an IANA
34assignment, and until that assignment is official, this implementation is
35not interoperable with other implementations (even future versions of this
36module) 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>.
58 51
59In addition to the core CBOR data format, this module implements a number 52In addition to the core CBOR data format, this module implements a
60of extensions, to support cyclic and self-referencing data structures 53number of extensions, to support cyclic and shared data structures (see
61(see C<allow_sharing>), string deduplication (see C<pack_strings>) and 54C<allow_sharing>), string deduplication (see C<pack_strings>) and scalar
62scalar references (always enabled). 55references (always enabled).
63 56
64The 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
65is 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.
66 59
67See 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
… …
71 64
72package CBOR::XS; 65package CBOR::XS;
73 66
74use common::sense; 67use common::sense;
75 68
76our $VERSION = 0.09; 69our $VERSION = '1.0';
77our @ISA = qw(Exporter); 70our @ISA = qw(Exporter);
78 71
79our @EXPORT = qw(encode_cbor decode_cbor); 72our @EXPORT = qw(encode_cbor decode_cbor);
80 73
81use Exporter; 74use Exporter;
… …
259function, C<CBOR::XS::default_filter>, is used. This function simply looks 252function, C<CBOR::XS::default_filter>, is used. This function simply looks
260up the tag in the C<%CBOR::XS::FILTER> hash. If an entry exists it must be 253up the tag in the C<%CBOR::XS::FILTER> hash. If an entry exists it must be
261a code reference that is called with tag and value, and is responsible for 254a code reference that is called with tag and value, and is responsible for
262decoding the value. If no entry exists, it returns no values. 255decoding the value. If no entry exists, it returns no values.
263 256
264Example: decode all tags not handled internally into CBOR::XS::Tagged 257Example: decode all tags not handled internally into C<CBOR::XS::Tagged>
265objects, with no other special handling (useful when working with 258objects, with no other special handling (useful when working with
266potentially "unsafe" CBOR data). 259potentially "unsafe" CBOR data).
267 260
268 CBOR::XS->new->filter (sub { })->decode ($cbor_data); 261 CBOR::XS->new->filter (sub { })->decode ($cbor_data);
269 262
… …
356=item tagged values 349=item tagged values
357 350
358Tagged items consists of a numeric tag and another CBOR value. 351Tagged items consists of a numeric tag and another CBOR value.
359 352
360See L<TAG HANDLING AND EXTENSIONS> and the description of C<< ->filter >> 353See L<TAG HANDLING AND EXTENSIONS> and the description of C<< ->filter >>
361for details. 354for details on which tags are handled how.
362 355
363=item anything else 356=item anything else
364 357
365Anything else (e.g. unsupported simple values) will raise a decoding 358Anything else (e.g. unsupported simple values) will raise a decoding
366error. 359error.
… …
369 362
370 363
371=head2 PERL -> CBOR 364=head2 PERL -> CBOR
372 365
373The mapping from Perl to CBOR is slightly more difficult, as Perl is a 366The mapping from Perl to CBOR is slightly more difficult, as Perl is a
374truly typeless language, so we can only guess which CBOR type is meant by 367typeless language. That means this module can only guess which CBOR type
375a Perl value. 368is meant by a perl value.
376 369
377=over 4 370=over 4
378 371
379=item hash references 372=item hash references
380 373
381Perl hash references become CBOR maps. As there is no inherent ordering in 374Perl hash references become CBOR maps. As there is no inherent ordering in
382hash keys (or CBOR maps), they will usually be encoded in a pseudo-random 375hash keys (or CBOR maps), they will usually be encoded in a pseudo-random
383order. 376order. This order can be different each time a hahs is encoded.
384 377
385Currently, tied hashes will use the indefinite-length format, while normal 378Currently, tied hashes will use the indefinite-length format, while normal
386hashes will use the fixed-length format. 379hashes will use the fixed-length format.
387 380
388=item array references 381=item array references
389 382
390Perl array references become fixed-length CBOR arrays. 383Perl array references become fixed-length CBOR arrays.
391 384
392=item other references 385=item other references
393 386
394Other unblessed references are generally not allowed and will cause an 387Other unblessed references will be represented using
395exception to be thrown, except for references to the integers C<0> and 388the indirection tag extension (tag value C<22098>,
396C<1>, which get turned into false and true in CBOR. 389L<http://cbor.schmorp.de/indirection>). CBOR decoders are guaranteed
390to be able to decode these values somehow, by either "doing the right
391thing", decoding into a generic tagged object, simply ignoring the tag, or
392something else.
397 393
398=item CBOR::XS::Tagged objects 394=item CBOR::XS::Tagged objects
399 395
400Objects of this type must be arrays consisting of a single C<[tag, value]> 396Objects of this type must be arrays consisting of a single C<[tag, value]>
401pair. The (numerical) tag will be encoded as a CBOR tag, the value will 397pair. The (numerical) tag will be encoded as a CBOR tag, the value will
402be encoded as appropriate for the value. You cna use C<CBOR::XS::tag> to 398be encoded as appropriate for the value. You must use C<CBOR::XS::tag> to
403create such objects. 399create such objects.
404 400
405=item Types::Serialiser::true, Types::Serialiser::false, Types::Serialiser::error 401=item Types::Serialiser::true, Types::Serialiser::false, Types::Serialiser::error
406 402
407These special values become CBOR true, CBOR false and CBOR undefined 403These special values become CBOR true, CBOR false and CBOR undefined
… …
523 519
524 sub URI::TO_CBOR { 520 sub URI::TO_CBOR {
525 my ($self) = @_; 521 my ($self) = @_;
526 my $uri = "$self"; # stringify uri 522 my $uri = "$self"; # stringify uri
527 utf8::upgrade $uri; # make sure it will be encoded as UTF-8 string 523 utf8::upgrade $uri; # make sure it will be encoded as UTF-8 string
528 CBOR::XS::tagged 32, "$_[0]" 524 CBOR::XS::tag 32, "$_[0]"
529 } 525 }
530 526
531This will encode URIs as a UTF-8 string with tag 32, which indicates an 527This will encode URIs as a UTF-8 string with tag 32, which indicates an
532URI. 528URI.
533 529

Diff Legend

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