… | |
… | |
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 | |
31 | WARNING! THIS IS A PRE-ALPHA RELEASE! IT WILL CRASH, CORRUPT YOUR DATA |
31 | WARNING! This module is very new, and not very well tested (that's up to |
32 | AND EAT YOUR CHILDREN! (Actually, apart from being untested and a bit |
32 | you to do). Furthermore, details of the implementation might change freely |
33 | feature-limited, it might already be useful). |
33 | before version 1.0. And lastly, the object serialisation protocol depends |
|
|
34 | on a pending IANA assignment, and until that assignment is official, this |
|
|
35 | implementation is not interoperable with other implementations (even |
|
|
36 | future versions of this module) until the assignment is done. |
|
|
37 | |
|
|
38 | You are still invited to try out CBOR, and this module. |
34 | |
39 | |
35 | This module converts Perl data structures to the Concise Binary Object |
40 | This module converts Perl data structures to the Concise Binary Object |
36 | Representation (CBOR) and vice versa. CBOR is a fast binary serialisation |
41 | Representation (CBOR) and vice versa. CBOR is a fast binary serialisation |
37 | format that aims to use a superset of the JSON data model, i.e. when you |
42 | format that aims to use a superset of the JSON data model, i.e. when you |
38 | can represent something in JSON, you should be able to represent it in |
43 | can represent something in JSON, you should be able to represent it in |
39 | CBOR. |
44 | CBOR. |
40 | |
45 | |
41 | This makes it a faster and more compact binary alternative to JSON, with |
46 | In short, CBOR is a faster and very compact binary alternative to JSON, |
42 | the added ability of supporting serialising of perl objects. |
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 |
|
|
49 | data later you might want to compare both formats first). |
43 | |
50 | |
44 | The primary goal of this module is to be I<correct> and the secondary goal |
51 | The primary goal of this module is to be I<correct> and the secondary goal |
45 | is to be I<fast>. To reach the latter goal it was written in C. |
52 | is to be I<fast>. To reach the latter goal it was written in C. |
46 | |
53 | |
47 | See MAPPING, below, on how CBOR::XS maps perl values to CBOR values and |
54 | See MAPPING, below, on how CBOR::XS maps perl values to CBOR values and |
… | |
… | |
51 | |
58 | |
52 | package CBOR::XS; |
59 | package CBOR::XS; |
53 | |
60 | |
54 | use common::sense; |
61 | use common::sense; |
55 | |
62 | |
56 | our $VERSION = 0.03; |
63 | our $VERSION = 0.06; |
57 | our @ISA = qw(Exporter); |
64 | our @ISA = qw(Exporter); |
58 | |
65 | |
59 | our @EXPORT = qw(encode_cbor decode_cbor); |
66 | our @EXPORT = qw(encode_cbor decode_cbor); |
60 | |
67 | |
61 | use Exporter; |
68 | use Exporter; |
… | |
… | |
222 | error). See the L<Types::Serialiser> manpage for details. |
229 | error). See the L<Types::Serialiser> manpage for details. |
223 | |
230 | |
224 | =item CBOR tag 256 (perl object) |
231 | =item CBOR tag 256 (perl object) |
225 | |
232 | |
226 | The tag value C<256> (TODO: pending iana registration) will be used |
233 | The tag value C<256> (TODO: pending iana registration) will be used |
227 | to deserialise a Perl object serialised with C<FREEZE>. See "OBJECT |
234 | to deserialise a Perl object serialised with C<FREEZE>. See L<OBJECT |
228 | SERIALISATION", below, for details. |
235 | SERIALISATION>, below, for details. |
229 | |
236 | |
230 | =item CBOR tag 55799 (magic header) |
237 | =item CBOR tag 55799 (magic header) |
231 | |
238 | |
232 | The tag 55799 is ignored (this tag implements the magic header). |
239 | The tag 55799 is ignored (this tag implements the magic header). |
233 | |
240 | |
… | |
… | |
276 | C<1>, which get turned into false and true in CBOR. |
283 | C<1>, which get turned into false and true in CBOR. |
277 | |
284 | |
278 | =item CBOR::XS::Tagged objects |
285 | =item CBOR::XS::Tagged objects |
279 | |
286 | |
280 | Objects of this type must be arrays consisting of a single C<[tag, value]> |
287 | Objects of this type must be arrays consisting of a single C<[tag, value]> |
281 | pair. The (numerical) tag will be encoded as a CBOR tag, the value will be |
288 | pair. The (numerical) tag will be encoded as a CBOR tag, the value will |
282 | encoded as appropriate for the value. |
289 | be encoded as appropriate for the value. You cna use C<CBOR::XS::tag> to |
|
|
290 | create such objects. |
283 | |
291 | |
284 | =item Types::Serialiser::true, Types::Serialiser::false, Types::Serialiser::error |
292 | =item Types::Serialiser::true, Types::Serialiser::false, Types::Serialiser::error |
285 | |
293 | |
286 | These special values become CBOR true, CBOR false and CBOR undefined |
294 | These special values become CBOR true, CBOR false and CBOR undefined |
287 | values, respectively. You can also use C<\1>, C<\0> and C<\undef> directly |
295 | values, respectively. You can also use C<\1>, C<\0> and C<\undef> directly |
288 | if you want. |
296 | if you want. |
289 | |
297 | |
290 | =item other blessed objects |
298 | =item other blessed objects |
291 | |
299 | |
292 | Other blessed objects are serialised via C<TO_CBOR> or C<FREEZE>. See |
300 | Other blessed objects are serialised via C<TO_CBOR> or C<FREEZE>. See |
293 | "OBJECT SERIALISATION", below, for details. |
301 | L<OBJECT SERIALISATION>, below, for details. |
294 | |
302 | |
295 | =item simple scalars |
303 | =item simple scalars |
296 | |
304 | |
297 | TODO |
305 | TODO |
298 | Simple Perl scalars (any scalar that is not a reference) are the most |
306 | Simple Perl scalars (any scalar that is not a reference) are the most |
… | |
… | |
446 | This string is available as C<$CBOR::XS::MAGIC>. This module does not |
454 | This string is available as C<$CBOR::XS::MAGIC>. This module does not |
447 | prepend this string tot he CBOR data it generates, but it will ignroe it |
455 | prepend this string tot he CBOR data it generates, but it will ignroe it |
448 | if present, so users can prepend this string as a "file type" indicator as |
456 | if present, so users can prepend this string as a "file type" indicator as |
449 | required. |
457 | required. |
450 | |
458 | |
|
|
459 | |
|
|
460 | =head1 THE CBOR::XS::Tagged CLASS |
|
|
461 | |
|
|
462 | CBOR has the concept of tagged values - any CBOR value can be tagged with |
|
|
463 | a numeric 64 bit number, which are centrally administered. |
|
|
464 | |
|
|
465 | C<CBOR::XS> handles a few tags internally when en- or decoding. You can |
|
|
466 | also create tags yourself by encoding C<CBOR::XS::Tagged> objects, and the |
|
|
467 | decoder will create C<CBOR::XS::Tagged> objects itself when it hits an |
|
|
468 | unknown tag. |
|
|
469 | |
|
|
470 | These objects are simply blessed array references - the first member of |
|
|
471 | the array being the numerical tag, the second being the value. |
|
|
472 | |
|
|
473 | You can interact with C<CBOR::XS::Tagged> objects in the following ways: |
|
|
474 | |
|
|
475 | =over 4 |
|
|
476 | |
|
|
477 | =item $tagged = CBOR::XS::tag $tag, $value |
|
|
478 | |
|
|
479 | This function(!) creates a new C<CBOR::XS::Tagged> object using the given |
|
|
480 | C<$tag> (0..2**64-1) to tag the given C<$value> (which can be any Perl |
|
|
481 | value that can be encoded in CBOR, including serialisable Perl objects and |
|
|
482 | C<CBOR::XS::Tagged> objects). |
|
|
483 | |
|
|
484 | =item $tagged->[0] |
|
|
485 | |
|
|
486 | =item $tagged->[0] = $new_tag |
|
|
487 | |
|
|
488 | =item $tag = $tagged->tag |
|
|
489 | |
|
|
490 | =item $new_tag = $tagged->tag ($new_tag) |
|
|
491 | |
|
|
492 | Access/mutate the tag. |
|
|
493 | |
|
|
494 | =item $tagged->[1] |
|
|
495 | |
|
|
496 | =item $tagged->[1] = $new_value |
|
|
497 | |
|
|
498 | =item $value = $tagged->value |
|
|
499 | |
|
|
500 | =item $new_value = $tagged->value ($new_value) |
|
|
501 | |
|
|
502 | Access/mutate the tagged value. |
|
|
503 | |
|
|
504 | =back |
|
|
505 | |
|
|
506 | =cut |
|
|
507 | |
|
|
508 | sub tag($$) { |
|
|
509 | bless [@_], CBOR::XS::Tagged::; |
|
|
510 | } |
|
|
511 | |
|
|
512 | sub CBOR::XS::Tagged::tag { |
|
|
513 | $_[0][0] = $_[1] if $#_; |
|
|
514 | $_[0][0] |
|
|
515 | } |
|
|
516 | |
|
|
517 | sub CBOR::XS::Tagged::value { |
|
|
518 | $_[0][1] = $_[1] if $#_; |
|
|
519 | $_[0][1] |
|
|
520 | } |
|
|
521 | |
|
|
522 | =head2 EXAMPLES |
|
|
523 | |
|
|
524 | Here are some examples of C<CBOR::XS::Tagged> uses to tag objects. |
|
|
525 | |
|
|
526 | You can look up CBOR tag value and emanings in the IANA registry at |
|
|
527 | L<http://www.iana.org/assignments/cbor-tags/cbor-tags.xhtml>. |
|
|
528 | |
|
|
529 | Prepend a magic header (C<$CBOR::XS::MAGIC>): |
|
|
530 | |
|
|
531 | my $cbor = encode_cbor CBOR::XS::tag 55799, $value; |
|
|
532 | # same as: |
|
|
533 | my $cbor = $CBOR::XS::MAGIC . encode_cbor $value; |
|
|
534 | |
|
|
535 | Serialise some URIs and a regex in an array: |
|
|
536 | |
|
|
537 | my $cbor = encode_cbor [ |
|
|
538 | (CBOR::XS::tag 32, "http://www.nethype.de/"), |
|
|
539 | (CBOR::XS::tag 32, "http://software.schmorp.de/"), |
|
|
540 | (CBOR::XS::tag 35, "^[Pp][Ee][Rr][lL]\$"), |
|
|
541 | ]; |
|
|
542 | |
|
|
543 | Wrap CBOR data in CBOR: |
|
|
544 | |
|
|
545 | my $cbor_cbor = encode_cbor |
|
|
546 | CBOR::XS::tag 24, |
|
|
547 | encode_cbor [1, 2, 3]; |
451 | |
548 | |
452 | =head1 CBOR and JSON |
549 | =head1 CBOR and JSON |
453 | |
550 | |
454 | CBOR is supposed to implement a superset of the JSON data model, and is, |
551 | CBOR is supposed to implement a superset of the JSON data model, and is, |
455 | with some coercion, able to represent all JSON texts (something that other |
552 | with some coercion, able to represent all JSON texts (something that other |