Wrong Encoding Result

[cfan8]

var target = {
    msg: 12345,
    target: "123hfsda",
    child: {
        msg: 2138912,
        txt: '12321sdhaifds6823rhisdfasdjsfjkasdfj',
        boo: true,
        arr: ['2132121331sdvsdadfs', 'sadfsdfafsadf', 'weqrswfsa', 'fsadfsadfa']
    }
};

Here is the object, using msgpack5, we have

131 163 109 115 103 205 48 57 166 116 97 114 103 101 116 168 49 50 51 104 102 115 100 97 165 99 104 105 108 100 132 163 109 115 103 206 0 32 163 32 163 116 120 116 217 36 49 50 51 50 49 115 100 104 97 105 102 100 115 54 56 50 51 114 104 105 115 100 102 97 115 100 106 115 102 106 107 97 115 100 102 106 163 98 111 111 195 163 97 114 114 148 179 50 49 51 50 49 50 49 51 51 49 115 100 118 115 100 97 100 102 115 173 115 97 100 102 115 100 102 97 102 115 97 100 102 169 119 101 113 114 115 119 102 115 97 170 102 115 97 100 102 115 97 100 102 97

using node-msgpack, we have

131 163 109 115 103 205 48 57 166 116 97 114 103 101 116 168 49 50 51 104 102 115 100 97 165 99 104 105 108 100 132 163 109 115 103 206 0 32 163 32 163 116 120 116 218 0 36 49 50 51 50 49 115 100 104 97 105 102 100 115 54 56 50 51 114 104 105 115 100 102 97 115 100 106 115 102 106 107 97 115 100 102 106 163 98 111 111 195 163 97 114 114 148 179 50 49 51 50 49 50 49 51 51 49 115 100 118 115 100 97 100 102 115 173 115 97 100 102 115 100 102 97 102 115 97 100 102 169 119 101 113 114 115 119 102 115 97 170 102 115 97 100 102 115 97 100 102 97

There is one bit difference in the boundary of target.child.msg and target.child.txt. On http://msgpack-json-editor.com/ the first one is not valid, while the latter is.

[mcollina]

node-msgpack and msgpack5 implements two different formats, with the latter implementing the latest version of the spec. Ence, compatibility with node-msgpack was never a goal.

Please verify with another library that implements the same version of the format. Il giorno ven 21 ago 2015 alle 04:59 cfan8 notifications@github.com ha scritto:

var target = { msg: 12345, target: "123hfsda", child: { msg: 2138912, txt: '12321sdhaifds6823rhisdfasdjsfjkasdfj', boo: true, arr: ['2132121331sdvsdadfs', 'sadfsdfafsadf', 'weqrswfsa', 'fsadfsadfa'] } };

Here is the object, using msgpack5, we have

131 163 109 115 103 205 48 57 166 116 97 114 103 101 116 168 49 50 51 104 102 115 100 97 165 99 104 105 108 100 132 163 109 115 103 206 0 32 163 32 163 116 120 116 217 36 49 50 51 50 49 115 100 104 97 105 102 100 115 54 56 50 51 114 104 105 115 100 102 97 115 100 106 115 102 106 107 97 115 100 102 106 163 98 111 111 195 163 97 114 114 148 179 50 49 51 50 49 50 49 51 51 49 115 100 118 115 100 97 100 102 115 173 115 97 100 102 115 100 102 97 102 115 97 100 102 169 119 101 113 114 115 119 102 115 97 170 102 115 97 100 102 115 97 100 102 97

using node-msgpack, we have

131 163 109 115 103 205 48 57 166 116 97 114 103 101 116 168 49 50 51 104 102 115 100 97 165 99 104 105 108 100 132 163 109 115 103 206 0 32 163 32 163 116 120 116 218 0 36 49 50 51 50 49 115 100 104 97 105 102 100 115 54 56 50 51 114 104 105 115 100 102 97 115 100 106 115 102 106 107 97 115 100 102 106 163 98 111 111 195 163 97 114 114 148 179 50 49 51 50 49 50 49 51 51 49 115 100 118 115 100 97 100 102 115 173 115 97 100 102 115 100 102 97 102 115 97 100 102 169 119 101 113 114 115 119 102 115 97 170 102 115 97 100 102 115 97 100 102 97

There is one bit difference in the boundary of target.child.msg and target.child.txt. On http://msgpack-json-editor.com/ the first one is not valid, while the latter is.

— Reply to this email directly or view it on GitHub https://github.com/mcollina/msgpack5/issues/32.