… | |
… | |
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 module is very new, and not very well tested (that's up |
|
|
32 | to you to do). Furthermore, details of the implementation might change |
|
|
33 | freely before version 1.0. And lastly, most extensions depend on an IANA |
|
|
34 | assignment, and until that assignment is official, this implementation is |
|
|
35 | not interoperable with other implementations (even future versions of this |
|
|
36 | module) until the assignment is done. |
|
|
37 | |
|
|
38 | You are still invited to try out CBOR, and this module. |
|
|
39 | |
|
|
40 | This module converts Perl data structures to the Concise Binary Object |
31 | This module converts Perl data structures to the Concise Binary Object |
41 | Representation (CBOR) and vice versa. CBOR is a fast binary serialisation |
32 | Representation (CBOR) and vice versa. CBOR is a fast binary serialisation |
42 | format that aims to use a superset of the JSON data model, i.e. when you |
33 | format that aims to use an (almost) superset of the JSON data model, i.e. |
43 | can represent something in JSON, you should be able to represent it in |
34 | when you can represent something useful in JSON, you should be able to |
44 | CBOR. |
35 | represent it in CBOR. |
45 | |
36 | |
46 | In short, CBOR is a faster and very compact binary alternative to JSON, |
37 | In short, CBOR is a faster and quite compact binary alternative to JSON, |
47 | with the added ability of supporting serialisation of Perl objects. (JSON |
38 | 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 |
39 | often compresses better than CBOR though, so if you plan to compress the |
49 | data later you might want to compare both formats first). |
40 | data later and speed is less important you might want to compare both |
|
|
41 | formats first). |
50 | |
42 | |
51 | To give you a general idea about speed, with texts in the megabyte range, |
43 | To give you a general idea about speed, with texts in the megabyte range, |
52 | C<CBOR::XS> usually encodes roughly twice as fast as L<Storable> or |
44 | C<CBOR::XS> usually encodes roughly twice as fast as L<Storable> or |
53 | L<JSON::XS> and decodes about 15%-30% faster than those. The shorter the |
45 | L<JSON::XS> and decodes about 15%-30% faster than those. The shorter the |
54 | data, the worse L<Storable> performs in comparison. |
46 | data, the worse L<Storable> performs in comparison. |
55 | |
47 | |
56 | As for compactness, C<CBOR::XS> encoded data structures are usually about |
48 | Regarding compactness, C<CBOR::XS>-encoded data structures are usually |
57 | 20% smaller than the same data encoded as (compact) JSON or L<Storable>. |
49 | about 20% smaller than the same data encoded as (compact) JSON or |
|
|
50 | L<Storable>. |
58 | |
51 | |
59 | In addition to the core CBOR data format, this module implements a number |
52 | In addition to the core CBOR data format, this module implements a |
60 | of extensions, to support cyclic and self-referencing data structures |
53 | number of extensions, to support cyclic and shared data structures (see |
61 | (see C<allow_sharing>), string deduplication (see C<allow_stringref>) and |
54 | C<allow_sharing>), string deduplication (see C<pack_strings>) and scalar |
62 | scalar references (always enabled). |
55 | references (always enabled). |
63 | |
56 | |
64 | The primary goal of this module is to be I<correct> and the secondary goal |
57 | The primary goal of this module is to be I<correct> and the secondary goal |
65 | is to be I<fast>. To reach the latter goal it was written in C. |
58 | is to be I<fast>. To reach the latter goal it was written in C. |
66 | |
59 | |
67 | See MAPPING, below, on how CBOR::XS maps perl values to CBOR values and |
60 | See MAPPING, below, on how CBOR::XS maps perl values to CBOR values and |
… | |
… | |
71 | |
64 | |
72 | package CBOR::XS; |
65 | package CBOR::XS; |
73 | |
66 | |
74 | use common::sense; |
67 | use common::sense; |
75 | |
68 | |
76 | our $VERSION = 0.08; |
69 | our $VERSION = '1.0'; |
77 | our @ISA = qw(Exporter); |
70 | our @ISA = qw(Exporter); |
78 | |
71 | |
79 | our @EXPORT = qw(encode_cbor decode_cbor); |
72 | our @EXPORT = qw(encode_cbor decode_cbor); |
80 | |
73 | |
81 | use Exporter; |
74 | use Exporter; |
… | |
… | |
186 | as an array, is referenced multiple times), but instead will emit a |
179 | as an array, is referenced multiple times), but instead will emit a |
187 | reference to the earlier value. |
180 | reference to the earlier value. |
188 | |
181 | |
189 | This means that such values will only be encoded once, and will not result |
182 | This means that such values will only be encoded once, and will not result |
190 | in a deep cloning of the value on decode, in decoders supporting the value |
183 | in a deep cloning of the value on decode, in decoders supporting the value |
191 | sharing extension. |
184 | sharing extension. This also makes it possible to encode cyclic data |
|
|
185 | structures. |
192 | |
186 | |
193 | It is recommended to leave it off unless you know your |
187 | It is recommended to leave it off unless you know your |
194 | communication partner supports the value sharing extensions to CBOR |
188 | communication partner supports the value sharing extensions to CBOR |
195 | (http://cbor.schmorp.de/value-sharing). |
189 | (L<http://cbor.schmorp.de/value-sharing>), as without decoder support, the |
|
|
190 | resulting data structure might be unusable. |
196 | |
191 | |
197 | Detecting shared values incurs a runtime overhead when values are encoded |
192 | Detecting shared values incurs a runtime overhead when values are encoded |
198 | that have a reference counter large than one, and might unnecessarily |
193 | that have a reference counter large than one, and might unnecessarily |
199 | increase the encoded size, as potentially shared values are encode as |
194 | increase the encoded size, as potentially shared values are encode as |
200 | sharable whether or not they are actually shared. |
195 | sharable whether or not they are actually shared. |
201 | |
196 | |
202 | At the moment, only targets of references can be shared (e.g. scalars, |
197 | At the moment, only targets of references can be shared (e.g. scalars, |
203 | arrays or hashes pointed to by a reference). Weirder constructs, such as |
198 | arrays or hashes pointed to by a reference). Weirder constructs, such as |
204 | an array with multiple "copies" of the I<same> string, which are hard but |
199 | an array with multiple "copies" of the I<same> string, which are hard but |
205 | not impossible to create in Perl, are not supported (this is the same as |
200 | not impossible to create in Perl, are not supported (this is the same as |
206 | for L<Storable>). |
201 | with L<Storable>). |
207 | |
202 | |
208 | If C<$enable> is false (the default), then C<encode> will encode |
203 | If C<$enable> is false (the default), then C<encode> will encode shared |
209 | exception when it encounters anything it cannot encode as CBOR. |
204 | data structures repeatedly, unsharing them in the process. Cyclic data |
|
|
205 | structures cannot be encoded in this mode. |
210 | |
206 | |
211 | This option does not affect C<decode> in any way - shared values and |
207 | This option does not affect C<decode> in any way - shared values and |
212 | references will always be decoded properly if present. |
208 | references will always be decoded properly if present. |
213 | |
209 | |
214 | =item $cbor = $cbor->allow_stringref ([$enable]) |
210 | =item $cbor = $cbor->pack_strings ([$enable]) |
215 | |
211 | |
216 | =item $enabled = $cbor->get_allow_stringref |
212 | =item $enabled = $cbor->get_pack_strings |
217 | |
213 | |
218 | If C<$enable> is true (or missing), then C<encode> will try not to encode |
214 | If C<$enable> is true (or missing), then C<encode> will try not to encode |
219 | the same string twice, but will instead encode a reference to the string |
215 | the same string twice, but will instead encode a reference to the string |
220 | instead. Depending on your data format. this can save a lot of space, but |
216 | instead. Depending on your data format, this can save a lot of space, but |
221 | also results in a very large runtime overhead (expect encoding times to be |
217 | also results in a very large runtime overhead (expect encoding times to be |
222 | 2-4 times as high as without). |
218 | 2-4 times as high as without). |
223 | |
219 | |
224 | It is recommended to leave it off unless you know your |
220 | It is recommended to leave it off unless you know your |
225 | communications partner supports the stringref extension to CBOR |
221 | communications partner supports the stringref extension to CBOR |
226 | (http://cbor.schmorp.de/stringref). |
222 | (L<http://cbor.schmorp.de/stringref>), as without decoder support, the |
|
|
223 | resulting data structure might not be usable. |
227 | |
224 | |
228 | If C<$enable> is false (the default), then C<encode> will encode |
225 | If C<$enable> is false (the default), then C<encode> will encode strings |
229 | exception when it encounters anything it cannot encode as CBOR. |
226 | the standard CBOR way. |
230 | |
227 | |
231 | This option does not affect C<decode> in any way - string references will |
228 | This option does not affect C<decode> in any way - string references will |
232 | always be decoded properly if present. |
229 | always be decoded properly if present. |
233 | |
230 | |
234 | =item $cbor = $cbor->filter ([$cb->($tag, $value)]) |
231 | =item $cbor = $cbor->filter ([$cb->($tag, $value)]) |
235 | |
232 | |
236 | =item $cb_or_undef = $cbor->get_filter |
233 | =item $cb_or_undef = $cbor->get_filter |
237 | |
234 | |
238 | TODO |
235 | Sets or replaces the tagged value decoding filter (when C<$cb> is |
|
|
236 | specified) or clears the filter (if no argument or C<undef> is provided). |
|
|
237 | |
|
|
238 | The filter callback is called only during decoding, when a non-enforced |
|
|
239 | tagged value has been decoded (see L<TAG HANDLING AND EXTENSIONS> for a |
|
|
240 | list of enforced tags). For specific tags, it's often better to provide a |
|
|
241 | default converter using the C<%CBOR::XS::FILTER> hash (see below). |
|
|
242 | |
|
|
243 | The first argument is the numerical tag, the second is the (decoded) value |
|
|
244 | that has been tagged. |
|
|
245 | |
|
|
246 | The filter function should return either exactly one value, which will |
|
|
247 | replace the tagged value in the decoded data structure, or no values, |
|
|
248 | which will result in default handling, which currently means the decoder |
|
|
249 | creates a C<CBOR::XS::Tagged> object to hold the tag and the value. |
|
|
250 | |
|
|
251 | When the filter is cleared (the default state), the default filter |
|
|
252 | function, C<CBOR::XS::default_filter>, is used. This function simply looks |
|
|
253 | up the tag in the C<%CBOR::XS::FILTER> hash. If an entry exists it must be |
|
|
254 | a code reference that is called with tag and value, and is responsible for |
|
|
255 | decoding the value. If no entry exists, it returns no values. |
|
|
256 | |
|
|
257 | Example: decode all tags not handled internally into C<CBOR::XS::Tagged> |
|
|
258 | objects, with no other special handling (useful when working with |
|
|
259 | potentially "unsafe" CBOR data). |
|
|
260 | |
|
|
261 | CBOR::XS->new->filter (sub { })->decode ($cbor_data); |
|
|
262 | |
|
|
263 | Example: provide a global filter for tag 1347375694, converting the value |
|
|
264 | into some string form. |
|
|
265 | |
|
|
266 | $CBOR::XS::FILTER{1347375694} = sub { |
|
|
267 | my ($tag, $value); |
|
|
268 | |
|
|
269 | "tag 1347375694 value $value" |
|
|
270 | }; |
239 | |
271 | |
240 | =item $cbor_data = $cbor->encode ($perl_scalar) |
272 | =item $cbor_data = $cbor->encode ($perl_scalar) |
241 | |
273 | |
242 | Converts the given Perl data structure (a scalar value) to its CBOR |
274 | Converts the given Perl data structure (a scalar value) to its CBOR |
243 | representation. |
275 | representation. |
… | |
… | |
284 | CBOR integers become (numeric) perl scalars. On perls without 64 bit |
316 | CBOR integers become (numeric) perl scalars. On perls without 64 bit |
285 | support, 64 bit integers will be truncated or otherwise corrupted. |
317 | support, 64 bit integers will be truncated or otherwise corrupted. |
286 | |
318 | |
287 | =item byte strings |
319 | =item byte strings |
288 | |
320 | |
289 | Byte strings will become octet strings in Perl (the byte values 0..255 |
321 | Byte strings will become octet strings in Perl (the Byte values 0..255 |
290 | will simply become characters of the same value in Perl). |
322 | will simply become characters of the same value in Perl). |
291 | |
323 | |
292 | =item UTF-8 strings |
324 | =item UTF-8 strings |
293 | |
325 | |
294 | UTF-8 strings in CBOR will be decoded, i.e. the UTF-8 octets will be |
326 | UTF-8 strings in CBOR will be decoded, i.e. the UTF-8 octets will be |
… | |
… | |
317 | =item tagged values |
349 | =item tagged values |
318 | |
350 | |
319 | Tagged items consists of a numeric tag and another CBOR value. |
351 | Tagged items consists of a numeric tag and another CBOR value. |
320 | |
352 | |
321 | See L<TAG HANDLING AND EXTENSIONS> and the description of C<< ->filter >> |
353 | See L<TAG HANDLING AND EXTENSIONS> and the description of C<< ->filter >> |
322 | for details. |
354 | for details on which tags are handled how. |
323 | |
355 | |
324 | =item anything else |
356 | =item anything else |
325 | |
357 | |
326 | Anything else (e.g. unsupported simple values) will raise a decoding |
358 | Anything else (e.g. unsupported simple values) will raise a decoding |
327 | error. |
359 | error. |
… | |
… | |
330 | |
362 | |
331 | |
363 | |
332 | =head2 PERL -> CBOR |
364 | =head2 PERL -> CBOR |
333 | |
365 | |
334 | The mapping from Perl to CBOR is slightly more difficult, as Perl is a |
366 | The mapping from Perl to CBOR is slightly more difficult, as Perl is a |
335 | truly typeless language, so we can only guess which CBOR type is meant by |
367 | typeless language. That means this module can only guess which CBOR type |
336 | a Perl value. |
368 | is meant by a perl value. |
337 | |
369 | |
338 | =over 4 |
370 | =over 4 |
339 | |
371 | |
340 | =item hash references |
372 | =item hash references |
341 | |
373 | |
342 | Perl hash references become CBOR maps. As there is no inherent ordering in |
374 | Perl hash references become CBOR maps. As there is no inherent ordering in |
343 | hash keys (or CBOR maps), they will usually be encoded in a pseudo-random |
375 | hash keys (or CBOR maps), they will usually be encoded in a pseudo-random |
344 | order. |
376 | order. This order can be different each time a hahs is encoded. |
345 | |
377 | |
346 | Currently, tied hashes will use the indefinite-length format, while normal |
378 | Currently, tied hashes will use the indefinite-length format, while normal |
347 | hashes will use the fixed-length format. |
379 | hashes will use the fixed-length format. |
348 | |
380 | |
349 | =item array references |
381 | =item array references |
350 | |
382 | |
351 | Perl array references become fixed-length CBOR arrays. |
383 | Perl array references become fixed-length CBOR arrays. |
352 | |
384 | |
353 | =item other references |
385 | =item other references |
354 | |
386 | |
355 | Other unblessed references are generally not allowed and will cause an |
387 | Other unblessed references will be represented using |
356 | exception to be thrown, except for references to the integers C<0> and |
388 | the indirection tag extension (tag value C<22098>, |
357 | C<1>, which get turned into false and true in CBOR. |
389 | L<http://cbor.schmorp.de/indirection>). CBOR decoders are guaranteed |
|
|
390 | to be able to decode these values somehow, by either "doing the right |
|
|
391 | thing", decoding into a generic tagged object, simply ignoring the tag, or |
|
|
392 | something else. |
358 | |
393 | |
359 | =item CBOR::XS::Tagged objects |
394 | =item CBOR::XS::Tagged objects |
360 | |
395 | |
361 | Objects of this type must be arrays consisting of a single C<[tag, value]> |
396 | Objects of this type must be arrays consisting of a single C<[tag, value]> |
362 | pair. The (numerical) tag will be encoded as a CBOR tag, the value will |
397 | pair. The (numerical) tag will be encoded as a CBOR tag, the value will |
363 | be encoded as appropriate for the value. You cna use C<CBOR::XS::tag> to |
398 | be encoded as appropriate for the value. You must use C<CBOR::XS::tag> to |
364 | create such objects. |
399 | create such objects. |
365 | |
400 | |
366 | =item Types::Serialiser::true, Types::Serialiser::false, Types::Serialiser::error |
401 | =item Types::Serialiser::true, Types::Serialiser::false, Types::Serialiser::error |
367 | |
402 | |
368 | These special values become CBOR true, CBOR false and CBOR undefined |
403 | These special values become CBOR true, CBOR false and CBOR undefined |
… | |
… | |
385 | # dump as number |
420 | # dump as number |
386 | encode_cbor [2] # yields [2] |
421 | encode_cbor [2] # yields [2] |
387 | encode_cbor [-3.0e17] # yields [-3e+17] |
422 | encode_cbor [-3.0e17] # yields [-3e+17] |
388 | my $value = 5; encode_cbor [$value] # yields [5] |
423 | my $value = 5; encode_cbor [$value] # yields [5] |
389 | |
424 | |
390 | # used as string, so dump as string |
425 | # used as string, so dump as string (either byte or text) |
391 | print $value; |
426 | print $value; |
392 | encode_cbor [$value] # yields ["5"] |
427 | encode_cbor [$value] # yields ["5"] |
393 | |
428 | |
394 | # undef becomes null |
429 | # undef becomes null |
395 | encode_cbor [undef] # yields [null] |
430 | encode_cbor [undef] # yields [null] |
… | |
… | |
398 | |
433 | |
399 | my $x = 3.1; # some variable containing a number |
434 | my $x = 3.1; # some variable containing a number |
400 | "$x"; # stringified |
435 | "$x"; # stringified |
401 | $x .= ""; # another, more awkward way to stringify |
436 | $x .= ""; # another, more awkward way to stringify |
402 | print $x; # perl does it for you, too, quite often |
437 | print $x; # perl does it for you, too, quite often |
|
|
438 | |
|
|
439 | You can force whether a string ie encoded as byte or text string by using |
|
|
440 | C<utf8::upgrade> and C<utf8::downgrade>): |
|
|
441 | |
|
|
442 | utf8::upgrade $x; # encode $x as text string |
|
|
443 | utf8::downgrade $x; # encode $x as byte string |
|
|
444 | |
|
|
445 | Perl doesn't define what operations up- and downgrade strings, so if the |
|
|
446 | difference between byte and text is important, you should up- or downgrade |
|
|
447 | your string as late as possible before encoding. |
403 | |
448 | |
404 | You can force the type to be a CBOR number by numifying it: |
449 | You can force the type to be a CBOR number by numifying it: |
405 | |
450 | |
406 | my $x = "3"; # some variable containing a string |
451 | my $x = "3"; # some variable containing a string |
407 | $x += 0; # numify it, ensuring it will be dumped as a number |
452 | $x += 0; # numify it, ensuring it will be dumped as a number |
… | |
… | |
420 | |
465 | |
421 | =back |
466 | =back |
422 | |
467 | |
423 | =head2 OBJECT SERIALISATION |
468 | =head2 OBJECT SERIALISATION |
424 | |
469 | |
|
|
470 | This module implements both a CBOR-specific and the generic |
|
|
471 | L<Types::Serialier> object serialisation protocol. The following |
|
|
472 | subsections explain both methods. |
|
|
473 | |
|
|
474 | =head3 ENCODING |
|
|
475 | |
425 | This module knows two way to serialise a Perl object: The CBOR-specific |
476 | This module knows two way to serialise a Perl object: The CBOR-specific |
426 | way, and the generic way. |
477 | way, and the generic way. |
427 | |
478 | |
428 | Whenever the encoder encounters a Perl object that it cnanot serialise |
479 | Whenever the encoder encounters a Perl object that it cannot serialise |
429 | directly (most of them), it will first look up the C<TO_CBOR> method on |
480 | directly (most of them), it will first look up the C<TO_CBOR> method on |
430 | it. |
481 | it. |
431 | |
482 | |
432 | If it has a C<TO_CBOR> method, it will call it with the object as only |
483 | If it has a C<TO_CBOR> method, it will call it with the object as only |
433 | argument, and expects exactly one return value, which it will then |
484 | argument, and expects exactly one return value, which it will then |
… | |
… | |
439 | |
490 | |
440 | The C<FREEZE> method can return any number of values (i.e. zero or |
491 | The C<FREEZE> method can return any number of values (i.e. zero or |
441 | more). These will be encoded as CBOR perl object, together with the |
492 | more). These will be encoded as CBOR perl object, together with the |
442 | classname. |
493 | classname. |
443 | |
494 | |
|
|
495 | These methods I<MUST NOT> change the data structure that is being |
|
|
496 | serialised. Failure to comply to this can result in memory corruption - |
|
|
497 | and worse. |
|
|
498 | |
444 | If an object supports neither C<TO_CBOR> nor C<FREEZE>, encoding will fail |
499 | If an object supports neither C<TO_CBOR> nor C<FREEZE>, encoding will fail |
445 | with an error. |
500 | with an error. |
446 | |
501 | |
|
|
502 | =head3 DECODING |
|
|
503 | |
447 | Objects encoded via C<TO_CBOR> cannot be automatically decoded, but |
504 | Objects encoded via C<TO_CBOR> cannot (normally) be automatically decoded, |
448 | objects encoded via C<FREEZE> can be decoded using the following protocol: |
505 | but objects encoded via C<FREEZE> can be decoded using the following |
|
|
506 | protocol: |
449 | |
507 | |
450 | When an encoded CBOR perl object is encountered by the decoder, it will |
508 | When an encoded CBOR perl object is encountered by the decoder, it will |
451 | look up the C<THAW> method, by using the stored classname, and will fail |
509 | look up the C<THAW> method, by using the stored classname, and will fail |
452 | if the method cannot be found. |
510 | if the method cannot be found. |
453 | |
511 | |
454 | After the lookup it will call the C<THAW> method with the stored classname |
512 | After the lookup it will call the C<THAW> method with the stored classname |
455 | as first argument, the constant string C<CBOR> as second argument, and all |
513 | as first argument, the constant string C<CBOR> as second argument, and all |
456 | values returned by C<FREEZE> as remaining arguments. |
514 | values returned by C<FREEZE> as remaining arguments. |
457 | |
515 | |
458 | =head4 EXAMPLES |
516 | =head3 EXAMPLES |
459 | |
517 | |
460 | Here is an example C<TO_CBOR> method: |
518 | Here is an example C<TO_CBOR> method: |
461 | |
519 | |
462 | sub My::Object::TO_CBOR { |
520 | sub My::Object::TO_CBOR { |
463 | my ($obj) = @_; |
521 | my ($obj) = @_; |
… | |
… | |
474 | |
532 | |
475 | sub URI::TO_CBOR { |
533 | sub URI::TO_CBOR { |
476 | my ($self) = @_; |
534 | my ($self) = @_; |
477 | my $uri = "$self"; # stringify uri |
535 | my $uri = "$self"; # stringify uri |
478 | utf8::upgrade $uri; # make sure it will be encoded as UTF-8 string |
536 | utf8::upgrade $uri; # make sure it will be encoded as UTF-8 string |
479 | CBOR::XS::tagged 32, "$_[0]" |
537 | CBOR::XS::tag 32, "$_[0]" |
480 | } |
538 | } |
481 | |
539 | |
482 | This will encode URIs as a UTF-8 string with tag 32, which indicates an |
540 | This will encode URIs as a UTF-8 string with tag 32, which indicates an |
483 | URI. |
541 | URI. |
484 | |
542 | |
… | |
… | |
640 | These tags are always handled when decoding, and their handling cannot be |
698 | These tags are always handled when decoding, and their handling cannot be |
641 | overriden by the user. |
699 | overriden by the user. |
642 | |
700 | |
643 | =over 4 |
701 | =over 4 |
644 | |
702 | |
645 | =item <unassigned> (perl-object, L<http://cbor.schmorp.de/perl-object>) |
703 | =item 26 (perl-object, L<http://cbor.schmorp.de/perl-object>) |
646 | |
704 | |
647 | These tags are automatically created (and decoded) for serialisable |
705 | These tags are automatically created (and decoded) for serialisable |
648 | objects using the C<FREEZE/THAW> methods (the L<Types::Serialier> object |
706 | objects using the C<FREEZE/THAW> methods (the L<Types::Serialier> object |
649 | serialisation protocol). See L<OBJECT SERIALISATION> for details. |
707 | serialisation protocol). See L<OBJECT SERIALISATION> for details. |
650 | |
708 | |
651 | =item <unassigned>, <unassigned> (sharable, sharedref, L <http://cbor.schmorp.de/value-sharing>) |
709 | =item 28, 29 (sharable, sharedref, L <http://cbor.schmorp.de/value-sharing>) |
652 | |
710 | |
653 | These tags are automatically decoded when encountered, resulting in |
711 | These tags are automatically decoded when encountered, resulting in |
654 | shared values in the decoded object. They are only encoded, however, when |
712 | shared values in the decoded object. They are only encoded, however, when |
655 | C<allow_sharable> is enabled. |
713 | C<allow_sharable> is enabled. |
656 | |
714 | |
657 | =item <unassigned>, <unassigned> (stringref-namespace, stringref, L <http://cbor.schmorp.de/stringref>) |
715 | =item 256, 25 (stringref-namespace, stringref, L <http://cbor.schmorp.de/stringref>) |
658 | |
716 | |
659 | These tags are automatically decoded when encountered. They are only |
717 | These tags are automatically decoded when encountered. They are only |
660 | encoded, however, when C<allow_stringref> is enabled. |
718 | encoded, however, when C<pack_strings> is enabled. |
661 | |
719 | |
662 | =item 22098 (indirection, L<http://cbor.schmorp.de/indirection>) |
720 | =item 22098 (indirection, L<http://cbor.schmorp.de/indirection>) |
663 | |
721 | |
664 | This tag is automatically generated when a reference are encountered (with |
722 | This tag is automatically generated when a reference are encountered (with |
665 | the exception of hash and array refernces). It is converted to a reference |
723 | the exception of hash and array refernces). It is converted to a reference |
… | |
… | |
670 | This value is not generated on encoding (unless explicitly requested by |
728 | This value is not generated on encoding (unless explicitly requested by |
671 | the user), and is simply ignored when decoding. |
729 | the user), and is simply ignored when decoding. |
672 | |
730 | |
673 | =back |
731 | =back |
674 | |
732 | |
675 | =head2 OPTIONAL TAGS |
733 | =head2 NON-ENFORCED TAGS |
676 | |
734 | |
677 | These tags have default filters provided when decoding. Their handling can |
735 | These tags have default filters provided when decoding. Their handling can |
678 | be overriden by changing the C<%CBOR::XS::FILTER> entry for the tag, or by |
736 | be overriden by changing the C<%CBOR::XS::FILTER> entry for the tag, or by |
679 | providing a custom C<filter> function when decoding. |
737 | providing a custom C<filter> callback when decoding. |
680 | |
738 | |
681 | When they result in decoding into a specific Perl class, the module |
739 | When they result in decoding into a specific Perl class, the module |
682 | usually provides a corresponding C<TO_CBOR> method as well. |
740 | usually provides a corresponding C<TO_CBOR> method as well. |
683 | |
741 | |
684 | When any of these need to load additional modules that are not part of the |
742 | When any of these need to load additional modules that are not part of the |
… | |
… | |
826 | Only the double data type is supported for NV data types - when Perl uses |
884 | Only the double data type is supported for NV data types - when Perl uses |
827 | long double to represent floating point values, they might not be encoded |
885 | long double to represent floating point values, they might not be encoded |
828 | properly. Half precision types are accepted, but not encoded. |
886 | properly. Half precision types are accepted, but not encoded. |
829 | |
887 | |
830 | Strict mode and canonical mode are not implemented. |
888 | Strict mode and canonical mode are not implemented. |
|
|
889 | |
|
|
890 | |
|
|
891 | =head1 LIMITATIONS ON PERLS WITHOUT 64-BIT INTEGER SUPPORT |
|
|
892 | |
|
|
893 | On perls that were built without 64 bit integer support (these are rare |
|
|
894 | nowadays, even on 32 bit architectures), support for any kind of 64 bit |
|
|
895 | integer in CBOR is very limited - most likely, these 64 bit values will |
|
|
896 | be truncated, corrupted, or otherwise not decoded correctly. This also |
|
|
897 | includes string, array and map sizes that are stored as 64 bit integers. |
831 | |
898 | |
832 | |
899 | |
833 | =head1 THREADS |
900 | =head1 THREADS |
834 | |
901 | |
835 | This module is I<not> guaranteed to be thread safe and there are no |
902 | This module is I<not> guaranteed to be thread safe and there are no |