GitHub / msgpack/msgpack issues and pull requests
#214 - 64-bit binary support
Issue -
State: open - Opened by cdolan over 9 years ago
- 8 comments
#208 - Some thoughts and considerations while evaluating MsgPack
Issue -
State: open - Opened by mlsomers over 9 years ago
- 2 comments
#206 - BigInteger support
Issue -
State: open - Opened by dedee almost 10 years ago
- 54 comments
#202 - MsgPack Schema
Issue -
State: open - Opened by kostja about 10 years ago
- 14 comments
#198 - Packed arrays
Issue -
State: open - Opened by letmaik about 10 years ago
- 6 comments
#195 - Determine version of spec
Issue -
State: open - Opened by rikvdh over 10 years ago
- 32 comments
#194 - MIME type
Issue -
State: closed - Opened by kyrias over 10 years ago
- 32 comments
#189 - Specification does not state license
Issue -
State: open - Opened by dachaac over 10 years ago
- 11 comments
#180 - CBOR - seems like a "better" MsgPack
Issue -
State: closed - Opened by dimzon almost 11 years ago
- 2 comments
#172 - Why is MsgPack big endian?
Issue -
State: closed - Opened by DaveVdE over 11 years ago
- 3 comments
#171 - field name compact
Issue -
State: open - Opened by jkindle over 11 years ago
- 4 comments
#170 - Minor typos in spec.md (fixnum --> fixint)
Issue -
State: closed - Opened by motegi over 11 years ago
#165 - Provide version numbers for the old and new specifications
Pull Request -
State: open - Opened by jodastephen over 11 years ago
- 1 comment
#160 - Proposal: Indexed string extension type
Issue -
State: closed - Opened by jblazquez over 11 years ago
- 7 comments
#130 - Support timestamp as new spec-defined inter-operable extension type.
Issue -
State: open - Opened by ugorji over 12 years ago
- 47 comments
#129 - MessagePack should be developed in an open process
Issue -
State: closed - Opened by cabo over 12 years ago
- 28 comments
Labels: Spec