New Str encoding broke compatibility with 0.49 decoding

[maxatome]

Since ada320e the Bin encoding has been added.
So from this commit, utf8 strings are encoded using Str (old Raw) format and others with Bin one.
It appears that one can not choose to disable this new encoding and stay with the old Raw (Str) one.
It is problematic in a client/server environment, where Data::MessagePack versions are not necessarily the same at a given time, on both side...
I encounter this case (server sends binary non-utf8 strings using 0.50 and client uses 0.49), so unless a "str_as_bin" (or something like that) option is added, one have to stay with 0.49 version in such cases and not upgrade any more.

[syohex]

Yes, Data::MessagePack implements new MessagePack specification since version 0.50(Extension type is not supported yet). Please upgrade both server and client if you use version Data::MessagePack 0.50.

[maxatome]

It is too bad to not be able to keep the backward compatibility while taking advantage of bugs corrections of new versions... Sometimes one can not easily upgrade the client side (embedded environments for example) :(

[frsyuki]

Here is the guideline for libraries to support new format:
https://github.com/msgpack/msgpack/blob/master/spec.md#impl-upgrade

Deserialization support is desired in a minor update.
Change of serializers should come later as a new major release.

[syohex]

I released version 0.51 and 1.00. 0.51 reverts Str/Bin. If you want to use old specification please use it.

[dolmen]

For users of Data::MessagePack with Dist::Zilla, here is how to specify the prereq for the legacy msgpack behaviour:

[Prereqs]
Data::MessagePack = < 1.00, != 0.49_01, != 0.50