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.19 by root, Wed Nov 20 01:09:46 2013 UTC vs.
Revision 1.44 by root, Mon Apr 27 20:21:53 2015 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 to
32you to do). Furthermore, details of the implementation might change freely
33before version 1.0. And lastly, the object serialisation protocol depends
34on a pending IANA assignment, and until that assignment is official, this
35implementation is not interoperable with other implementations (even
36future versions of this module) 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>.
51
52In addition to the core CBOR data format, this module implements a
53number of extensions, to support cyclic and shared data structures
54(see C<allow_sharing> and C<allow_cycles>), string deduplication (see
55C<pack_strings>) and scalar references (always enabled).
58 56
59The 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
60is 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.
61 59
62See 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
66 64
67package CBOR::XS; 65package CBOR::XS;
68 66
69use common::sense; 67use common::sense;
70 68
71our $VERSION = 0.08; 69our $VERSION = 1.3;
72our @ISA = qw(Exporter); 70our @ISA = qw(Exporter);
73 71
74our @EXPORT = qw(encode_cbor decode_cbor); 72our @EXPORT = qw(encode_cbor decode_cbor);
75 73
76use Exporter; 74use Exporter;
113strings. All boolean flags described below are by default I<disabled>. 111strings. All boolean flags described below are by default I<disabled>.
114 112
115The mutators for flags all return the CBOR object again and thus calls can 113The mutators for flags all return the CBOR object again and thus calls can
116be chained: 114be chained:
117 115
118#TODO
119 my $cbor = CBOR::XS->new->encode ({a => [1,2]}); 116 my $cbor = CBOR::XS->new->encode ({a => [1,2]});
120 117
121=item $cbor = $cbor->max_depth ([$maximum_nesting_depth]) 118=item $cbor = $cbor->max_depth ([$maximum_nesting_depth])
122 119
123=item $max_depth = $cbor->get_max_depth 120=item $max_depth = $cbor->get_max_depth
171exception when it encounters anything it cannot encode as CBOR. 168exception when it encounters anything it cannot encode as CBOR.
172 169
173This option does not affect C<decode> in any way, and it is recommended to 170This option does not affect C<decode> in any way, and it is recommended to
174leave it off unless you know your communications partner. 171leave it off unless you know your communications partner.
175 172
176=item $cbor = $cbor->allow_sharable ([$enable]) 173=item $cbor = $cbor->allow_sharing ([$enable])
177 174
178=item $enabled = $cbor->get_allow_sharable 175=item $enabled = $cbor->get_allow_sharing
179 176
180If C<$enable> is true (or missing), then C<encode> will not double-encode 177If C<$enable> is true (or missing), then C<encode> will not double-encode
181values that have been seen before (e.g. when the same object, such as an 178values that have been referenced before (e.g. when the same object, such
182array, is referenced multiple times), but instead will emit a reference to 179as an array, is referenced multiple times), but instead will emit a
183the earlier value. 180reference to the earlier value.
184 181
185This means that such values will only be encoded once, and will not result 182This means that such values will only be encoded once, and will not result
186in a deep cloning of the value on decode, in decoders supporting the value 183in a deep cloning of the value on decode, in decoders supporting the value
187sharing extension. 184sharing extension. This also makes it possible to encode cyclic data
185structures (which need C<allow_cycles> to ne enabled to be decoded by this
186module).
187
188It is recommended to leave it off unless you know your
189communication partner supports the value sharing extensions to CBOR
190(L<http://cbor.schmorp.de/value-sharing>), as without decoder support, the
191resulting data structure might be unusable.
188 192
189Detecting shared values incurs a runtime overhead when values are encoded 193Detecting shared values incurs a runtime overhead when values are encoded
190that have a reference counter large than one, and might unnecessarily 194that have a reference counter large than one, and might unnecessarily
191increase the encoded size, as potentially shared values are encode as 195increase the encoded size, as potentially shared values are encode as
192sharable whether or not they are actually shared. 196shareable whether or not they are actually shared.
193 197
194At the moment, all shared values will be detected, even weird and unusual 198At the moment, only targets of references can be shared (e.g. scalars,
195cases, such as an array with multiple "copies" of the I<same> scalar, 199arrays or hashes pointed to by a reference). Weirder constructs, such as
196which are hard but not impossible to create in Perl (L<Storable> for 200an array with multiple "copies" of the I<same> string, which are hard but
197example doesn't handle these cases). If this turns out ot be a performance 201not impossible to create in Perl, are not supported (this is the same as
198issue then future versions might limit the shared value detection to 202with L<Storable>).
199references only.
200 203
201If C<$enable> is false (the default), then C<encode> will encode 204If C<$enable> is false (the default), then C<encode> will encode shared
202exception when it encounters anything it cannot encode as CBOR. 205data structures repeatedly, unsharing them in the process. Cyclic data
206structures cannot be encoded in this mode.
203 207
204This option does not affect C<decode> in any way - shared values and 208This option does not affect C<decode> in any way - shared values and
205references will always be decoded properly if present. It is recommended 209references will always be decoded properly if present.
206to leave it off unless you know your communications partner supports the 210
207value sharing extensions to CBOR (http://cbor.schmorp.de/value-sharing). 211=item $cbor = $cbor->allow_cycles ([$enable])
212
213=item $enabled = $cbor->get_allow_cycles
214
215If C<$enable> is true (or missing), then C<decode> will happily decode
216self-referential (cyclic) data structures. By default these will not be
217decoded, as they need manual cleanup to avoid memory leaks, so code that
218isn't prepared for this will not leak memory.
219
220If C<$enable> is false (the default), then C<decode> will throw an error
221when it encounters a self-referential/cyclic data structure.
222
223FUTURE DIRECTION: the motivation behind this option is to avoid I<real>
224cycles - future versions of this module might chose to decode cyclic data
225structures using weak references when this option is off, instead of
226throwing an error.
227
228This option does not affect C<encode> in any way - shared values and
229references will always be encoded properly if present.
230
231=item $cbor = $cbor->pack_strings ([$enable])
232
233=item $enabled = $cbor->get_pack_strings
234
235If C<$enable> is true (or missing), then C<encode> will try not to encode
236the same string twice, but will instead encode a reference to the string
237instead. Depending on your data format, this can save a lot of space, but
238also results in a very large runtime overhead (expect encoding times to be
2392-4 times as high as without).
240
241It is recommended to leave it off unless you know your
242communications partner supports the stringref extension to CBOR
243(L<http://cbor.schmorp.de/stringref>), as without decoder support, the
244resulting data structure might not be usable.
245
246If C<$enable> is false (the default), then C<encode> will encode strings
247the standard CBOR way.
248
249This option does not affect C<decode> in any way - string references will
250always be decoded properly if present.
251
252=item $cbor = $cbor->validate_utf8 ([$enable])
253
254=item $enabled = $cbor->get_validate_utf8
255
256If C<$enable> is true (or missing), then C<decode> will validate that
257elements (text strings) containing UTF-8 data in fact contain valid UTF-8
258data (instead of blindly accepting it). This validation obviously takes
259extra time during decoding.
260
261The concept of "valid UTF-8" used is perl's concept, which is a superset
262of the official UTF-8.
263
264If C<$enable> is false (the default), then C<decode> will blindly accept
265UTF-8 data, marking them as valid UTF-8 in the resulting data structure
266regardless of whether thats true or not.
267
268Perl isn't too happy about corrupted UTF-8 in strings, but should
269generally not crash or do similarly evil things. Extensions might be not
270so forgiving, so it's recommended to turn on this setting if you receive
271untrusted CBOR.
272
273This option does not affect C<encode> in any way - strings that are
274supposedly valid UTF-8 will simply be dumped into the resulting CBOR
275string without checking whether that is, in fact, true or not.
276
277=item $cbor = $cbor->filter ([$cb->($tag, $value)])
278
279=item $cb_or_undef = $cbor->get_filter
280
281Sets or replaces the tagged value decoding filter (when C<$cb> is
282specified) or clears the filter (if no argument or C<undef> is provided).
283
284The filter callback is called only during decoding, when a non-enforced
285tagged value has been decoded (see L<TAG HANDLING AND EXTENSIONS> for a
286list of enforced tags). For specific tags, it's often better to provide a
287default converter using the C<%CBOR::XS::FILTER> hash (see below).
288
289The first argument is the numerical tag, the second is the (decoded) value
290that has been tagged.
291
292The filter function should return either exactly one value, which will
293replace the tagged value in the decoded data structure, or no values,
294which will result in default handling, which currently means the decoder
295creates a C<CBOR::XS::Tagged> object to hold the tag and the value.
296
297When the filter is cleared (the default state), the default filter
298function, C<CBOR::XS::default_filter>, is used. This function simply looks
299up the tag in the C<%CBOR::XS::FILTER> hash. If an entry exists it must be
300a code reference that is called with tag and value, and is responsible for
301decoding the value. If no entry exists, it returns no values.
302
303Example: decode all tags not handled internally into C<CBOR::XS::Tagged>
304objects, with no other special handling (useful when working with
305potentially "unsafe" CBOR data).
306
307 CBOR::XS->new->filter (sub { })->decode ($cbor_data);
308
309Example: provide a global filter for tag 1347375694, converting the value
310into some string form.
311
312 $CBOR::XS::FILTER{1347375694} = sub {
313 my ($tag, $value);
314
315 "tag 1347375694 value $value"
316 };
208 317
209=item $cbor_data = $cbor->encode ($perl_scalar) 318=item $cbor_data = $cbor->encode ($perl_scalar)
210 319
211Converts the given Perl data structure (a scalar value) to its CBOR 320Converts the given Perl data structure (a scalar value) to its CBOR
212representation. 321representation.
226and you need to know where the first CBOR string ends amd the next one 335and you need to know where the first CBOR string ends amd the next one
227starts. 336starts.
228 337
229 CBOR::XS->new->decode_prefix ("......") 338 CBOR::XS->new->decode_prefix ("......")
230 => ("...", 3) 339 => ("...", 3)
340
341=back
342
343=head2 INCREMENTAL PARSING
344
345In some cases, there is the need for incremental parsing of JSON
346texts. While this module always has to keep both CBOR text and resulting
347Perl data structure in memory at one time, it does allow you to parse a
348CBOR stream incrementally, using a similar to using "decode_prefix" to see
349if a full CBOR object is available, but is much more efficient.
350
351It basically works by parsing as much of a CBOR string as possible - if
352the CBOR data is not complete yet, the pasrer will remember where it was,
353to be able to restart when more data has been accumulated. Once enough
354data is available to either decode a complete CBOR value or raise an
355error, a real decode will be attempted.
356
357A typical use case would be a network protocol that consists of sending
358and receiving CBOR-encoded messages. The solution that works with CBOR and
359about anything else is by prepending a length to every CBOR value, so the
360receiver knows how many octets to read. More compact (and slightly slower)
361would be to just send CBOR values back-to-back, as C<CBOR::XS> knows where
362a CBOR value ends, and doesn't need an explicit length.
363
364The following methods help with this:
365
366=over 4
367
368=item @decoded = $cbor->incr_parse ($buffer)
369
370This method attempts to decode exactly one CBOR value from the beginning
371of the given C<$buffer>. The value is removed from the C<$buffer> on
372success. When C<$buffer> doesn't contain a complete value yet, it returns
373nothing. Finally, when the C<$buffer> doesn't start with something
374that could ever be a valid CBOR value, it raises an exception, just as
375C<decode> would. In the latter case the decoder state is undefined and
376must be reset before being able to parse further.
377
378This method modifies the C<$buffer> in place. When no CBOR value can be
379decoded, the decoder stores the current string offset. On the next call,
380continues decoding at the place where it stopped before. For this to make
381sense, the C<$buffer> must begin with the same octets as on previous
382unsuccessful calls.
383
384You can call this method in scalar context, in which case it either
385returns a decoded value or C<undef>. This makes it impossible to
386distinguish between CBOR null values (which decode to C<undef>) and an
387unsuccessful decode, which is often acceptable.
388
389=item @decoded = $cbor->incr_parse_multiple ($buffer)
390
391Same as C<incr_parse>, but attempts to decode as many CBOR values as
392possible in one go, instead of at most one. Calls to C<incr_parse> and
393C<incr_parse_multiple> can be interleaved.
394
395=item $cbor->incr_reset
396
397Resets the incremental decoder. This throws away any saved state, so that
398subsequent calls to C<incr_parse> or C<incr_parse_multiple> start to parse
399a new CBOR value from the beginning of the C<$buffer> again.
400
401This method can be caled at any time, but it I<must> be called if you want
402to change your C<$buffer> or there was a decoding error and you want to
403reuse the C<$cbor> object for future incremental parsings.
231 404
232=back 405=back
233 406
234 407
235=head1 MAPPING 408=head1 MAPPING
253CBOR integers become (numeric) perl scalars. On perls without 64 bit 426CBOR integers become (numeric) perl scalars. On perls without 64 bit
254support, 64 bit integers will be truncated or otherwise corrupted. 427support, 64 bit integers will be truncated or otherwise corrupted.
255 428
256=item byte strings 429=item byte strings
257 430
258Byte strings will become octet strings in Perl (the byte values 0..255 431Byte strings will become octet strings in Perl (the Byte values 0..255
259will simply become characters of the same value in Perl). 432will simply become characters of the same value in Perl).
260 433
261=item UTF-8 strings 434=item UTF-8 strings
262 435
263UTF-8 strings in CBOR will be decoded, i.e. the UTF-8 octets will be 436UTF-8 strings in CBOR will be decoded, i.e. the UTF-8 octets will be
281C<Types:Serialiser::false> and C<Types::Serialiser::error>, 454C<Types:Serialiser::false> and C<Types::Serialiser::error>,
282respectively. They are overloaded to act almost exactly like the numbers 455respectively. They are overloaded to act almost exactly like the numbers
283C<1> and C<0> (for true and false) or to throw an exception on access (for 456C<1> and C<0> (for true and false) or to throw an exception on access (for
284error). See the L<Types::Serialiser> manpage for details. 457error). See the L<Types::Serialiser> manpage for details.
285 458
286=item CBOR tag 256 (perl object) 459=item tagged values
287 460
288The tag value C<256> (TODO: pending iana registration) will be used
289to deserialise a Perl object serialised with C<FREEZE>. See L<OBJECT
290SERIALISATION>, below, for details.
291
292=item CBOR tag 55799 (magic header)
293
294The tag 55799 is ignored (this tag implements the magic header).
295
296=item other CBOR tags
297
298Tagged items consists of a numeric tag and another CBOR value. Tags not 461Tagged items consists of a numeric tag and another CBOR value.
299handled internally are currently converted into a L<CBOR::XS::Tagged>
300object, which is simply a blessed array reference consisting of the
301numeric tag value followed by the (decoded) CBOR value.
302 462
303In the future, support for user-supplied conversions might get added. 463See L<TAG HANDLING AND EXTENSIONS> and the description of C<< ->filter >>
464for details on which tags are handled how.
304 465
305=item anything else 466=item anything else
306 467
307Anything else (e.g. unsupported simple values) will raise a decoding 468Anything else (e.g. unsupported simple values) will raise a decoding
308error. 469error.
311 472
312 473
313=head2 PERL -> CBOR 474=head2 PERL -> CBOR
314 475
315The mapping from Perl to CBOR is slightly more difficult, as Perl is a 476The mapping from Perl to CBOR is slightly more difficult, as Perl is a
316truly typeless language, so we can only guess which CBOR type is meant by 477typeless language. That means this module can only guess which CBOR type
317a Perl value. 478is meant by a perl value.
318 479
319=over 4 480=over 4
320 481
321=item hash references 482=item hash references
322 483
323Perl hash references become CBOR maps. As there is no inherent ordering in 484Perl hash references become CBOR maps. As there is no inherent ordering in
324hash keys (or CBOR maps), they will usually be encoded in a pseudo-random 485hash keys (or CBOR maps), they will usually be encoded in a pseudo-random
325order. 486order. This order can be different each time a hahs is encoded.
326 487
327Currently, tied hashes will use the indefinite-length format, while normal 488Currently, tied hashes will use the indefinite-length format, while normal
328hashes will use the fixed-length format. 489hashes will use the fixed-length format.
329 490
330=item array references 491=item array references
331 492
332Perl array references become fixed-length CBOR arrays. 493Perl array references become fixed-length CBOR arrays.
333 494
334=item other references 495=item other references
335 496
336Other unblessed references are generally not allowed and will cause an 497Other unblessed references will be represented using
337exception to be thrown, except for references to the integers C<0> and 498the indirection tag extension (tag value C<22098>,
338C<1>, which get turned into false and true in CBOR. 499L<http://cbor.schmorp.de/indirection>). CBOR decoders are guaranteed
500to be able to decode these values somehow, by either "doing the right
501thing", decoding into a generic tagged object, simply ignoring the tag, or
502something else.
339 503
340=item CBOR::XS::Tagged objects 504=item CBOR::XS::Tagged objects
341 505
342Objects of this type must be arrays consisting of a single C<[tag, value]> 506Objects of this type must be arrays consisting of a single C<[tag, value]>
343pair. The (numerical) tag will be encoded as a CBOR tag, the value will 507pair. The (numerical) tag will be encoded as a CBOR tag, the value will
344be encoded as appropriate for the value. You cna use C<CBOR::XS::tag> to 508be encoded as appropriate for the value. You must use C<CBOR::XS::tag> to
345create such objects. 509create such objects.
346 510
347=item Types::Serialiser::true, Types::Serialiser::false, Types::Serialiser::error 511=item Types::Serialiser::true, Types::Serialiser::false, Types::Serialiser::error
348 512
349These special values become CBOR true, CBOR false and CBOR undefined 513These special values become CBOR true, CBOR false and CBOR undefined
351if you want. 515if you want.
352 516
353=item other blessed objects 517=item other blessed objects
354 518
355Other blessed objects are serialised via C<TO_CBOR> or C<FREEZE>. See 519Other blessed objects are serialised via C<TO_CBOR> or C<FREEZE>. See
356L<OBJECT SERIALISATION>, below, for details. 520L<TAG HANDLING AND EXTENSIONS> for specific classes handled by this
521module, and L<OBJECT SERIALISATION> for generic object serialisation.
357 522
358=item simple scalars 523=item simple scalars
359 524
360TODO
361Simple Perl scalars (any scalar that is not a reference) are the most 525Simple Perl scalars (any scalar that is not a reference) are the most
362difficult objects to encode: CBOR::XS will encode undefined scalars as 526difficult objects to encode: CBOR::XS will encode undefined scalars as
363CBOR null values, scalars that have last been used in a string context 527CBOR null values, scalars that have last been used in a string context
364before encoding as CBOR strings, and anything else as number value: 528before encoding as CBOR strings, and anything else as number value:
365 529
366 # dump as number 530 # dump as number
367 encode_cbor [2] # yields [2] 531 encode_cbor [2] # yields [2]
368 encode_cbor [-3.0e17] # yields [-3e+17] 532 encode_cbor [-3.0e17] # yields [-3e+17]
369 my $value = 5; encode_cbor [$value] # yields [5] 533 my $value = 5; encode_cbor [$value] # yields [5]
370 534
371 # used as string, so dump as string 535 # used as string, so dump as string (either byte or text)
372 print $value; 536 print $value;
373 encode_cbor [$value] # yields ["5"] 537 encode_cbor [$value] # yields ["5"]
374 538
375 # undef becomes null 539 # undef becomes null
376 encode_cbor [undef] # yields [null] 540 encode_cbor [undef] # yields [null]
379 543
380 my $x = 3.1; # some variable containing a number 544 my $x = 3.1; # some variable containing a number
381 "$x"; # stringified 545 "$x"; # stringified
382 $x .= ""; # another, more awkward way to stringify 546 $x .= ""; # another, more awkward way to stringify
383 print $x; # perl does it for you, too, quite often 547 print $x; # perl does it for you, too, quite often
548
549You can force whether a string ie encoded as byte or text string by using
550C<utf8::upgrade> and C<utf8::downgrade>):
551
552 utf8::upgrade $x; # encode $x as text string
553 utf8::downgrade $x; # encode $x as byte string
554
555Perl doesn't define what operations up- and downgrade strings, so if the
556difference between byte and text is important, you should up- or downgrade
557your string as late as possible before encoding.
384 558
385You can force the type to be a CBOR number by numifying it: 559You can force the type to be a CBOR number by numifying it:
386 560
387 my $x = "3"; # some variable containing a string 561 my $x = "3"; # some variable containing a string
388 $x += 0; # numify it, ensuring it will be dumped as a number 562 $x += 0; # numify it, ensuring it will be dumped as a number
401 575
402=back 576=back
403 577
404=head2 OBJECT SERIALISATION 578=head2 OBJECT SERIALISATION
405 579
580This module implements both a CBOR-specific and the generic
581L<Types::Serialier> object serialisation protocol. The following
582subsections explain both methods.
583
584=head3 ENCODING
585
406This module knows two way to serialise a Perl object: The CBOR-specific 586This module knows two way to serialise a Perl object: The CBOR-specific
407way, and the generic way. 587way, and the generic way.
408 588
409Whenever the encoder encounters a Perl object that it cnanot serialise 589Whenever the encoder encounters a Perl object that it cannot serialise
410directly (most of them), it will first look up the C<TO_CBOR> method on 590directly (most of them), it will first look up the C<TO_CBOR> method on
411it. 591it.
412 592
413If it has a C<TO_CBOR> method, it will call it with the object as only 593If it has a C<TO_CBOR> method, it will call it with the object as only
414argument, and expects exactly one return value, which it will then 594argument, and expects exactly one return value, which it will then
420 600
421The C<FREEZE> method can return any number of values (i.e. zero or 601The C<FREEZE> method can return any number of values (i.e. zero or
422more). These will be encoded as CBOR perl object, together with the 602more). These will be encoded as CBOR perl object, together with the
423classname. 603classname.
424 604
605These methods I<MUST NOT> change the data structure that is being
606serialised. Failure to comply to this can result in memory corruption -
607and worse.
608
425If an object supports neither C<TO_CBOR> nor C<FREEZE>, encoding will fail 609If an object supports neither C<TO_CBOR> nor C<FREEZE>, encoding will fail
426with an error. 610with an error.
427 611
612=head3 DECODING
613
428Objects encoded via C<TO_CBOR> cannot be automatically decoded, but 614Objects encoded via C<TO_CBOR> cannot (normally) be automatically decoded,
429objects encoded via C<FREEZE> can be decoded using the following protocol: 615but objects encoded via C<FREEZE> can be decoded using the following
616protocol:
430 617
431When an encoded CBOR perl object is encountered by the decoder, it will 618When an encoded CBOR perl object is encountered by the decoder, it will
432look up the C<THAW> method, by using the stored classname, and will fail 619look up the C<THAW> method, by using the stored classname, and will fail
433if the method cannot be found. 620if the method cannot be found.
434 621
435After the lookup it will call the C<THAW> method with the stored classname 622After the lookup it will call the C<THAW> method with the stored classname
436as first argument, the constant string C<CBOR> as second argument, and all 623as first argument, the constant string C<CBOR> as second argument, and all
437values returned by C<FREEZE> as remaining arguments. 624values returned by C<FREEZE> as remaining arguments.
438 625
439=head4 EXAMPLES 626=head3 EXAMPLES
440 627
441Here is an example C<TO_CBOR> method: 628Here is an example C<TO_CBOR> method:
442 629
443 sub My::Object::TO_CBOR { 630 sub My::Object::TO_CBOR {
444 my ($obj) = @_; 631 my ($obj) = @_;
455 642
456 sub URI::TO_CBOR { 643 sub URI::TO_CBOR {
457 my ($self) = @_; 644 my ($self) = @_;
458 my $uri = "$self"; # stringify uri 645 my $uri = "$self"; # stringify uri
459 utf8::upgrade $uri; # make sure it will be encoded as UTF-8 string 646 utf8::upgrade $uri; # make sure it will be encoded as UTF-8 string
460 CBOR::XS::tagged 32, "$_[0]" 647 CBOR::XS::tag 32, "$_[0]"
461 } 648 }
462 649
463This will encode URIs as a UTF-8 string with tag 32, which indicates an 650This will encode URIs as a UTF-8 string with tag 32, which indicates an
464URI. 651URI.
465 652
601 CBOR::XS::tag 24, 788 CBOR::XS::tag 24,
602 encode_cbor [1, 2, 3]; 789 encode_cbor [1, 2, 3];
603 790
604=head1 TAG HANDLING AND EXTENSIONS 791=head1 TAG HANDLING AND EXTENSIONS
605 792
606This section describes how this module handles specific tagged values and 793This section describes how this module handles specific tagged values
607extensions. If a tag is not mentioned here, then the default handling 794and extensions. If a tag is not mentioned here and no additional filters
795are provided for it, then the default handling applies (creating a
608applies (creating a CBOR::XS::Tagged object on decoding, and only encoding 796CBOR::XS::Tagged object on decoding, and only encoding the tag when
609the tag when explicitly requested). 797explicitly requested).
798
799Tags not handled specifically are currently converted into a
800L<CBOR::XS::Tagged> object, which is simply a blessed array reference
801consisting of the numeric tag value followed by the (decoded) CBOR value.
610 802
611Future versions of this module reserve the right to special case 803Future versions of this module reserve the right to special case
612additional tags (such as bigfloat or base64url). 804additional tags (such as base64url).
805
806=head2 ENFORCED TAGS
807
808These tags are always handled when decoding, and their handling cannot be
809overriden by the user.
613 810
614=over 4 811=over 4
615 812
616=item <unassigned> (perl-object, L<http://cbor.schmorp.de/perl-object>) 813=item 26 (perl-object, L<http://cbor.schmorp.de/perl-object>)
617 814
618These tags are automatically created for serialisable objects using the 815These tags are automatically created (and decoded) for serialisable
619C<FREEZE/THAW> methods (the L<Types::Serialier> object serialisation 816objects using the C<FREEZE/THAW> methods (the L<Types::Serialier> object
620protocol). 817serialisation protocol). See L<OBJECT SERIALISATION> for details.
621 818
622=item <unassigned>, <unassigned> (sharable, sharedref, L <http://cbor.schmorp.de/value-sharing>) 819=item 28, 29 (shareable, sharedref, L <http://cbor.schmorp.de/value-sharing>)
623 820
624These tags are automatically decoded when encountered, resulting in 821These tags are automatically decoded when encountered (and they do not
822result in a cyclic data structure, see C<allow_cycles>), resulting in
625shared values in the decoded object. They are only encoded, however, when 823shared values in the decoded object. They are only encoded, however, when
626C<allow_sharable> is enabled. 824C<allow_sharing> is enabled.
825
826Not all shared values can be successfully decoded: values that reference
827themselves will I<currently> decode as C<undef> (this is not the same
828as a reference pointing to itself, which will be represented as a value
829that contains an indirect reference to itself - these will be decoded
830properly).
831
832Note that considerably more shared value data structures can be decoded
833than will be encoded - currently, only values pointed to by references
834will be shared, others will not. While non-reference shared values can be
835generated in Perl with some effort, they were considered too unimportant
836to be supported in the encoder. The decoder, however, will decode these
837values as shared values.
838
839=item 256, 25 (stringref-namespace, stringref, L <http://cbor.schmorp.de/stringref>)
840
841These tags are automatically decoded when encountered. They are only
842encoded, however, when C<pack_strings> is enabled.
627 843
628=item 22098 (indirection, L<http://cbor.schmorp.de/indirection>) 844=item 22098 (indirection, L<http://cbor.schmorp.de/indirection>)
629 845
630This tag is automatically generated when a reference are encountered (with 846This tag is automatically generated when a reference are encountered (with
631the exception of hash and array refernces). It is converted to a reference 847the exception of hash and array refernces). It is converted to a reference
635 851
636This value is not generated on encoding (unless explicitly requested by 852This value is not generated on encoding (unless explicitly requested by
637the user), and is simply ignored when decoding. 853the user), and is simply ignored when decoding.
638 854
639=back 855=back
856
857=head2 NON-ENFORCED TAGS
858
859These tags have default filters provided when decoding. Their handling can
860be overriden by changing the C<%CBOR::XS::FILTER> entry for the tag, or by
861providing a custom C<filter> callback when decoding.
862
863When they result in decoding into a specific Perl class, the module
864usually provides a corresponding C<TO_CBOR> method as well.
865
866When any of these need to load additional modules that are not part of the
867perl core distribution (e.g. L<URI>), it is (currently) up to the user to
868provide these modules. The decoding usually fails with an exception if the
869required module cannot be loaded.
870
871=over 4
872
873=item 0, 1 (date/time string, seconds since the epoch)
874
875These tags are decoded into L<Time::Piece> objects. The corresponding
876C<Time::Piece::TO_CBOR> method always encodes into tag 1 values currently.
877
878The L<Time::Piece> API is generally surprisingly bad, and fractional
879seconds are only accidentally kept intact, so watch out. On the plus side,
880the module comes with perl since 5.10, which has to count for something.
881
882=item 2, 3 (positive/negative bignum)
883
884These tags are decoded into L<Math::BigInt> objects. The corresponding
885C<Math::BigInt::TO_CBOR> method encodes "small" bigints into normal CBOR
886integers, and others into positive/negative CBOR bignums.
887
888=item 4, 5 (decimal fraction/bigfloat)
889
890Both decimal fractions and bigfloats are decoded into L<Math::BigFloat>
891objects. The corresponding C<Math::BigFloat::TO_CBOR> method I<always>
892encodes into a decimal fraction.
893
894CBOR cannot represent bigfloats with I<very> large exponents - conversion
895of such big float objects is undefined.
896
897Also, NaN and infinities are not encoded properly.
898
899=item 21, 22, 23 (expected later JSON conversion)
900
901CBOR::XS is not a CBOR-to-JSON converter, and will simply ignore these
902tags.
903
904=item 32 (URI)
905
906These objects decode into L<URI> objects. The corresponding
907C<URI::TO_CBOR> method again results in a CBOR URI value.
908
909=back
910
911=cut
912
913our %FILTER = (
914 # 0 # rfc4287 datetime, utf-8
915 # 1 # unix timestamp, any
916
917 2 => sub { # pos bigint
918 require Math::BigInt;
919 Math::BigInt->new ("0x" . unpack "H*", pop)
920 },
921
922 3 => sub { # neg bigint
923 require Math::BigInt;
924 -Math::BigInt->new ("0x" . unpack "H*", pop)
925 },
926
927 4 => sub { # decimal fraction, array
928 require Math::BigFloat;
929 Math::BigFloat->new ($_[1][1] . "E" . $_[1][0])
930 },
931
932 5 => sub { # bigfloat, array
933 require Math::BigFloat;
934 scalar Math::BigFloat->new ($_[1][1])->blsft ($_[1][0], 2)
935 },
936
937 21 => sub { pop }, # expected conversion to base64url encoding
938 22 => sub { pop }, # expected conversion to base64 encoding
939 23 => sub { pop }, # expected conversion to base16 encoding
940
941 # 24 # embedded cbor, byte string
942
943 32 => sub {
944 require URI;
945 URI->new (pop)
946 },
947
948 # 33 # base64url rfc4648, utf-8
949 # 34 # base64 rfc46484, utf-8
950 # 35 # regex pcre/ecma262, utf-8
951 # 36 # mime message rfc2045, utf-8
952);
640 953
641 954
642=head1 CBOR and JSON 955=head1 CBOR and JSON
643 956
644CBOR is supposed to implement a superset of the JSON data model, and is, 957CBOR is supposed to implement a superset of the JSON data model, and is,
706properly. Half precision types are accepted, but not encoded. 1019properly. Half precision types are accepted, but not encoded.
707 1020
708Strict mode and canonical mode are not implemented. 1021Strict mode and canonical mode are not implemented.
709 1022
710 1023
1024=head1 LIMITATIONS ON PERLS WITHOUT 64-BIT INTEGER SUPPORT
1025
1026On perls that were built without 64 bit integer support (these are rare
1027nowadays, even on 32 bit architectures, as all major Perl distributions
1028are built with 64 bit integer support), support for any kind of 64 bit
1029integer in CBOR is very limited - most likely, these 64 bit values will
1030be truncated, corrupted, or otherwise not decoded correctly. This also
1031includes string, array and map sizes that are stored as 64 bit integers.
1032
1033
711=head1 THREADS 1034=head1 THREADS
712 1035
713This module is I<not> guaranteed to be thread safe and there are no 1036This module is I<not> guaranteed to be thread safe and there are no
714plans to change this until Perl gets thread support (as opposed to the 1037plans to change this until Perl gets thread support (as opposed to the
715horribly slow so-called "threads" which are simply slow and bloated 1038horribly slow so-called "threads" which are simply slow and bloated
727Please refrain from using rt.cpan.org or any other bug reporting 1050Please refrain from using rt.cpan.org or any other bug reporting
728service. I put the contact address into my modules for a reason. 1051service. I put the contact address into my modules for a reason.
729 1052
730=cut 1053=cut
731 1054
1055our %FILTER = (
1056 0 => sub { # rfc4287 datetime, utf-8
1057 require Time::Piece;
1058 # Time::Piece::Strptime uses the "incredibly flexible date parsing routine"
1059 # from FreeBSD, which can't parse ISO 8601, RFC3339, RFC4287 or much of anything
1060 # else either. Whats incredibe over standard strptime totally escapes me.
1061 # doesn't do fractional times, either. sigh.
1062 # In fact, it's all a lie, it uses whatever strptime it wants, and of course,
1063 # they are all incomptible. The openbsd one simply ignores %z (but according to the
1064 # docs, it would be much more incredibly flexible indeed. If it worked, that is.).
1065 scalar eval {
1066 my $s = $_[1];
1067
1068 $s =~ s/Z$/+00:00/;
1069 $s =~ s/(\.[0-9]+)?([+-][0-9][0-9]):([0-9][0-9])$//
1070 or die;
1071
1072 my $b = $1 - ($2 * 60 + $3) * 60; # fractional part + offset. hopefully
1073 my $d = Time::Piece->strptime ($s, "%Y-%m-%dT%H:%M:%S");
1074
1075 Time::Piece::gmtime ($d->epoch + $b)
1076 } || die "corrupted CBOR date/time string ($_[0])";
1077 },
1078
1079 1 => sub { # seconds since the epoch, possibly fractional
1080 require Time::Piece;
1081 scalar Time::Piece::gmtime (pop)
1082 },
1083
1084 2 => sub { # pos bigint
1085 require Math::BigInt;
1086 Math::BigInt->new ("0x" . unpack "H*", pop)
1087 },
1088
1089 3 => sub { # neg bigint
1090 require Math::BigInt;
1091 -Math::BigInt->new ("0x" . unpack "H*", pop)
1092 },
1093
1094 4 => sub { # decimal fraction, array
1095 require Math::BigFloat;
1096 Math::BigFloat->new ($_[1][1] . "E" . $_[1][0])
1097 },
1098
1099 5 => sub { # bigfloat, array
1100 require Math::BigFloat;
1101 scalar Math::BigFloat->new ($_[1][1])->blsft ($_[1][0], 2)
1102 },
1103
1104 21 => sub { pop }, # expected conversion to base64url encoding
1105 22 => sub { pop }, # expected conversion to base64 encoding
1106 23 => sub { pop }, # expected conversion to base16 encoding
1107
1108 # 24 # embedded cbor, byte string
1109
1110 32 => sub {
1111 require URI;
1112 URI->new (pop)
1113 },
1114
1115 # 33 # base64url rfc4648, utf-8
1116 # 34 # base64 rfc46484, utf-8
1117 # 35 # regex pcre/ecma262, utf-8
1118 # 36 # mime message rfc2045, utf-8
1119);
1120
1121sub CBOR::XS::default_filter {
1122 &{ $FILTER{$_[0]} or return }
1123}
1124
1125sub URI::TO_CBOR {
1126 my $uri = $_[0]->as_string;
1127 utf8::upgrade $uri;
1128 tag 32, $uri
1129}
1130
1131sub Math::BigInt::TO_CBOR {
1132 if ($_[0] >= -2147483648 && $_[0] <= 2147483647) {
1133 $_[0]->numify
1134 } else {
1135 my $hex = substr $_[0]->as_hex, 2;
1136 $hex = "0$hex" if 1 & length $hex; # sigh
1137 tag $_[0] >= 0 ? 2 : 3, pack "H*", $hex
1138 }
1139}
1140
1141sub Math::BigFloat::TO_CBOR {
1142 my ($m, $e) = $_[0]->parts;
1143 tag 4, [$e->numify, $m]
1144}
1145
1146sub Time::Piece::TO_CBOR {
1147 tag 1, 0 + $_[0]->epoch
1148}
1149
732XSLoader::load "CBOR::XS", $VERSION; 1150XSLoader::load "CBOR::XS", $VERSION;
733 1151
734=head1 SEE ALSO 1152=head1 SEE ALSO
735 1153
736The L<JSON> and L<JSON::XS> modules that do similar, but human-readable, 1154The L<JSON> and L<JSON::XS> modules that do similar, but human-readable,

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines