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.8 by root, Sun Oct 27 22:48:12 2013 UTC vs.
Revision 1.21 by root, Wed Nov 20 16:29:02 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 IS A PRE-ALPHA RELEASE! IT WILL CRASH, CORRUPT YOUR DATA 31WARNING! This module is very new, and not very well tested (that's up
32AND EAT YOUR CHILDREN! (Actually, apart from being untested and a bit 32to you to do). Furthermore, details of the implementation might change
33feature-limited, it might already be useful). 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.
34 39
35This module converts Perl data structures to the Concise Binary Object 40This module converts Perl data structures to the Concise Binary Object
36Representation (CBOR) and vice versa. CBOR is a fast binary serialisation 41Representation (CBOR) and vice versa. CBOR is a fast binary serialisation
37format that aims to use a superset of the JSON data model, i.e. when you 42format that aims to use a superset of the JSON data model, i.e. when you
38can represent something in JSON, you should be able to represent it in 43can represent something in JSON, you should be able to represent it in
39CBOR. 44CBOR.
40 45
41This makes it a faster and more compact binary alternative to JSON, with 46In short, CBOR is a faster and very compact binary alternative to JSON,
42the added ability of supporting serialising of perl objects. 47with the added ability of supporting serialisation of Perl objects. (JSON
48often compresses better than CBOR though, so if you plan to compress the
49data later you might want to compare both formats first).
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
59In addition to the core CBOR data format, this module implements a number
60of extensions, to support cyclic and self-referencing data structures
61(see C<allow_sharing>), string deduplication (see C<allow_stringref>) and
62scalar references (always enabled).
43 63
44The primary goal of this module is to be I<correct> and the secondary goal 64The primary goal of this module is to be I<correct> and the secondary goal
45is to be I<fast>. To reach the latter goal it was written in C. 65is to be I<fast>. To reach the latter goal it was written in C.
46 66
47See MAPPING, below, on how CBOR::XS maps perl values to CBOR values and 67See MAPPING, below, on how CBOR::XS maps perl values to CBOR values and
51 71
52package CBOR::XS; 72package CBOR::XS;
53 73
54use common::sense; 74use common::sense;
55 75
56our $VERSION = 0.04; 76our $VERSION = 0.08;
57our @ISA = qw(Exporter); 77our @ISA = qw(Exporter);
58 78
59our @EXPORT = qw(encode_cbor decode_cbor); 79our @EXPORT = qw(encode_cbor decode_cbor);
60 80
61use Exporter; 81use Exporter;
142If no argument is given, the limit check will be deactivated (same as when 162If no argument is given, the limit check will be deactivated (same as when
143C<0> is specified). 163C<0> is specified).
144 164
145See SECURITY CONSIDERATIONS, below, for more info on why this is useful. 165See SECURITY CONSIDERATIONS, below, for more info on why this is useful.
146 166
167=item $cbor = $cbor->allow_unknown ([$enable])
168
169=item $enabled = $cbor->get_allow_unknown
170
171If C<$enable> is true (or missing), then C<encode> will I<not> throw an
172exception when it encounters values it cannot represent in CBOR (for
173example, filehandles) but instead will encode a CBOR C<error> value.
174
175If C<$enable> is false (the default), then C<encode> will throw an
176exception when it encounters anything it cannot encode as CBOR.
177
178This option does not affect C<decode> in any way, and it is recommended to
179leave it off unless you know your communications partner.
180
181=item $cbor = $cbor->allow_sharing ([$enable])
182
183=item $enabled = $cbor->get_allow_sharing
184
185If C<$enable> is true (or missing), then C<encode> will not double-encode
186values that have been referenced before (e.g. when the same object, such
187as an array, is referenced multiple times), but instead will emit a
188reference to the earlier value.
189
190This means that such values will only be encoded once, and will not result
191in a deep cloning of the value on decode, in decoders supporting the value
192sharing extension.
193
194It is recommended to leave it off unless you know your
195communication partner supports the value sharing extensions to CBOR
196(http://cbor.schmorp.de/value-sharing).
197
198Detecting shared values incurs a runtime overhead when values are encoded
199that have a reference counter large than one, and might unnecessarily
200increase the encoded size, as potentially shared values are encode as
201sharable whether or not they are actually shared.
202
203At the moment, only targets of references can be shared (e.g. scalars,
204arrays or hashes pointed to by a reference). Weirder constructs, such as
205an array with multiple "copies" of the I<same> string, which are hard but
206not impossible to create in Perl, are not supported (this is the same as
207for L<Storable>).
208
209If C<$enable> is false (the default), then C<encode> will encode
210exception when it encounters anything it cannot encode as CBOR.
211
212This option does not affect C<decode> in any way - shared values and
213references will always be decoded properly if present.
214
215=item $cbor = $cbor->allow_stringref ([$enable])
216
217=item $enabled = $cbor->get_allow_stringref
218
219If C<$enable> is true (or missing), then C<encode> will try not to encode
220the same string twice, but will instead encode a reference to the string
221instead. Depending on your data format. this can save a lot of space, but
222also results in a very large runtime overhead (expect encoding times to be
2232-4 times as high as without).
224
225It is recommended to leave it off unless you know your
226communications partner supports the stringref extension to CBOR
227(http://cbor.schmorp.de/stringref).
228
229If C<$enable> is false (the default), then C<encode> will encode
230exception when it encounters anything it cannot encode as CBOR.
231
232This option does not affect C<decode> in any way - string references will
233always be decoded properly if present.
234
147=item $cbor_data = $cbor->encode ($perl_scalar) 235=item $cbor_data = $cbor->encode ($perl_scalar)
148 236
149Converts the given Perl data structure (a scalar value) to its CBOR 237Converts the given Perl data structure (a scalar value) to its CBOR
150representation. 238representation.
151 239
222error). See the L<Types::Serialiser> manpage for details. 310error). See the L<Types::Serialiser> manpage for details.
223 311
224=item CBOR tag 256 (perl object) 312=item CBOR tag 256 (perl object)
225 313
226The tag value C<256> (TODO: pending iana registration) will be used 314The tag value C<256> (TODO: pending iana registration) will be used
227to deserialise a Perl object serialised with C<FREEZE>. See "OBJECT 315to deserialise a Perl object serialised with C<FREEZE>. See L<OBJECT
228SERIALISATION", below, for details. 316SERIALISATION>, below, for details.
229 317
230=item CBOR tag 55799 (magic header) 318=item CBOR tag 55799 (magic header)
231 319
232The tag 55799 is ignored (this tag implements the magic header). 320The tag 55799 is ignored (this tag implements the magic header).
233 321
276C<1>, which get turned into false and true in CBOR. 364C<1>, which get turned into false and true in CBOR.
277 365
278=item CBOR::XS::Tagged objects 366=item CBOR::XS::Tagged objects
279 367
280Objects of this type must be arrays consisting of a single C<[tag, value]> 368Objects of this type must be arrays consisting of a single C<[tag, value]>
281pair. The (numerical) tag will be encoded as a CBOR tag, the value will be 369pair. The (numerical) tag will be encoded as a CBOR tag, the value will
282encoded as appropriate for the value. 370be encoded as appropriate for the value. You cna use C<CBOR::XS::tag> to
371create such objects.
283 372
284=item Types::Serialiser::true, Types::Serialiser::false, Types::Serialiser::error 373=item Types::Serialiser::true, Types::Serialiser::false, Types::Serialiser::error
285 374
286These special values become CBOR true, CBOR false and CBOR undefined 375These special values become CBOR true, CBOR false and CBOR undefined
287values, respectively. You can also use C<\1>, C<\0> and C<\undef> directly 376values, respectively. You can also use C<\1>, C<\0> and C<\undef> directly
288if you want. 377if you want.
289 378
290=item other blessed objects 379=item other blessed objects
291 380
292Other blessed objects are serialised via C<TO_CBOR> or C<FREEZE>. See 381Other blessed objects are serialised via C<TO_CBOR> or C<FREEZE>. See
293"OBJECT SERIALISATION", below, for details. 382L<OBJECT SERIALISATION>, below, for details.
294 383
295=item simple scalars 384=item simple scalars
296 385
297TODO 386TODO
298Simple Perl scalars (any scalar that is not a reference) are the most 387Simple Perl scalars (any scalar that is not a reference) are the most
439=head1 MAGIC HEADER 528=head1 MAGIC HEADER
440 529
441There is no way to distinguish CBOR from other formats 530There is no way to distinguish CBOR from other formats
442programmatically. To make it easier to distinguish CBOR from other 531programmatically. To make it easier to distinguish CBOR from other
443formats, the CBOR specification has a special "magic string" that can be 532formats, the CBOR specification has a special "magic string" that can be
444prepended to any CBOR string without changing it's meaning. 533prepended to any CBOR string without changing its meaning.
445 534
446This string is available as C<$CBOR::XS::MAGIC>. This module does not 535This string is available as C<$CBOR::XS::MAGIC>. This module does not
447prepend this string tot he CBOR data it generates, but it will ignroe it 536prepend this string to the CBOR data it generates, but it will ignore it
448if present, so users can prepend this string as a "file type" indicator as 537if present, so users can prepend this string as a "file type" indicator as
449required. 538required.
539
540
541=head1 THE CBOR::XS::Tagged CLASS
542
543CBOR has the concept of tagged values - any CBOR value can be tagged with
544a numeric 64 bit number, which are centrally administered.
545
546C<CBOR::XS> handles a few tags internally when en- or decoding. You can
547also create tags yourself by encoding C<CBOR::XS::Tagged> objects, and the
548decoder will create C<CBOR::XS::Tagged> objects itself when it hits an
549unknown tag.
550
551These objects are simply blessed array references - the first member of
552the array being the numerical tag, the second being the value.
553
554You can interact with C<CBOR::XS::Tagged> objects in the following ways:
555
556=over 4
557
558=item $tagged = CBOR::XS::tag $tag, $value
559
560This function(!) creates a new C<CBOR::XS::Tagged> object using the given
561C<$tag> (0..2**64-1) to tag the given C<$value> (which can be any Perl
562value that can be encoded in CBOR, including serialisable Perl objects and
563C<CBOR::XS::Tagged> objects).
564
565=item $tagged->[0]
566
567=item $tagged->[0] = $new_tag
568
569=item $tag = $tagged->tag
570
571=item $new_tag = $tagged->tag ($new_tag)
572
573Access/mutate the tag.
574
575=item $tagged->[1]
576
577=item $tagged->[1] = $new_value
578
579=item $value = $tagged->value
580
581=item $new_value = $tagged->value ($new_value)
582
583Access/mutate the tagged value.
584
585=back
586
587=cut
588
589sub tag($$) {
590 bless [@_], CBOR::XS::Tagged::;
591}
592
593sub CBOR::XS::Tagged::tag {
594 $_[0][0] = $_[1] if $#_;
595 $_[0][0]
596}
597
598sub CBOR::XS::Tagged::value {
599 $_[0][1] = $_[1] if $#_;
600 $_[0][1]
601}
602
603=head2 EXAMPLES
604
605Here are some examples of C<CBOR::XS::Tagged> uses to tag objects.
606
607You can look up CBOR tag value and emanings in the IANA registry at
608L<http://www.iana.org/assignments/cbor-tags/cbor-tags.xhtml>.
609
610Prepend a magic header (C<$CBOR::XS::MAGIC>):
611
612 my $cbor = encode_cbor CBOR::XS::tag 55799, $value;
613 # same as:
614 my $cbor = $CBOR::XS::MAGIC . encode_cbor $value;
615
616Serialise some URIs and a regex in an array:
617
618 my $cbor = encode_cbor [
619 (CBOR::XS::tag 32, "http://www.nethype.de/"),
620 (CBOR::XS::tag 32, "http://software.schmorp.de/"),
621 (CBOR::XS::tag 35, "^[Pp][Ee][Rr][lL]\$"),
622 ];
623
624Wrap CBOR data in CBOR:
625
626 my $cbor_cbor = encode_cbor
627 CBOR::XS::tag 24,
628 encode_cbor [1, 2, 3];
629
630=head1 TAG HANDLING AND EXTENSIONS
631
632This section describes how this module handles specific tagged values and
633extensions. If a tag is not mentioned here, then the default handling
634applies (creating a CBOR::XS::Tagged object on decoding, and only encoding
635the tag when explicitly requested).
636
637Future versions of this module reserve the right to special case
638additional tags (such as bigfloat or base64url).
639
640=over 4
641
642=item <unassigned> (perl-object, L<http://cbor.schmorp.de/perl-object>)
643
644These tags are automatically created for serialisable objects using the
645C<FREEZE/THAW> methods (the L<Types::Serialier> object serialisation
646protocol).
647
648=item <unassigned>, <unassigned> (sharable, sharedref, L <http://cbor.schmorp.de/value-sharing>)
649
650These tags are automatically decoded when encountered, resulting in
651shared values in the decoded object. They are only encoded, however, when
652C<allow_sharable> is enabled.
653
654=item <unassigned>, <unassigned> (stringref-namespace, stringref, L <http://cbor.schmorp.de/stringref>)
655
656These tags are automatically decoded when encountered. They are only
657encoded, however, when C<allow_stringref> is enabled.
658
659=item 22098 (indirection, L<http://cbor.schmorp.de/indirection>)
660
661This tag is automatically generated when a reference are encountered (with
662the exception of hash and array refernces). It is converted to a reference
663when decoding.
664
665=item 55799 (self-describe CBOR, RFC 7049)
666
667This value is not generated on encoding (unless explicitly requested by
668the user), and is simply ignored when decoding.
669
670=back
450 671
451 672
452=head1 CBOR and JSON 673=head1 CBOR and JSON
453 674
454CBOR is supposed to implement a superset of the JSON data model, and is, 675CBOR is supposed to implement a superset of the JSON data model, and is,

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines