You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a Date object is created in Javascript (new Date()), and is serialized with MessagePack, then PHP will fail to deserialize with the following message: PHP Warning: [msgpack] (php_msgpack_unserialize) Parse error
This happens if the Date object is by itself, or part of another object. It also happens if the serialization is done with either of the two javascript libraries listed on https://msgpack.org
Are there plans to do so, or is this library no longer being maintained? I noticed there hasn't been a release since December 6, 2016. I would generally prefer an extension as they are likely to have better performance (and one of the benefits of MessagePack is better performance), but if the PHP implementation is the one being maintained, then that would be a better choice. Is it recommended that the PHP implementation be used for new projects instead of the PHP extension?
If a
Date
object is created in Javascript (new Date()
), and is serialized with MessagePack, then PHP will fail to deserialize with the following message:PHP Warning: [msgpack] (php_msgpack_unserialize) Parse error
This happens if the
Date
object is by itself, or part of another object. It also happens if the serialization is done with either of the two javascript libraries listed on https://msgpack.orgDate
as ext 8 (0xc7).Date
as timestamp 64 (0xd7).MessagePack Specification: https://github.com/msgpack/msgpack/blob/master/spec.md
Expected Behavior: Javascript
Date
is deserialized to PHPDateTime
.The text was updated successfully, but these errors were encountered: