Sadayuki Furuhashi

I can propose following idea as an alternative approach: ``` N-dimentional array extension type is assigned to extension type 2 (TBD). +--------+--------+--------+--------+--------+--------+--------+--------+ | 0xc9 |ZZZZZZZZ|ZZZZZZZZ|ZZZZZZZZ|ZZZZZZZZ| 2 | type | D...

Yes. [Crawler](https://github.com/msgpack/website/blob/master/update-index.rb) may have a problem. Let me check. I hope it doesn't need a overhaul...

"x-" was deprecated by RFC 6648 which was published June 2012, but msgpack exists since February 2009. From Github code search, `application/x-msgpack` is commonly used. * [Use of application/x-msgpack](https://github.com/search?utf8=%E2%9C%93&q=%22application%2Fx-msgpack%22&type=Code) *...

I started crafting the application texts for https://www.iana.org/form/media-types based on RFC 6838. There're many examples I can refer to fill out the forms at [Media Types list](https://www.iana.org/assignments/media-types/media-types.xhtml). Especially, [applicatoin/json](https://www.iana.org/assignments/media-types/application/json) and...

Forms that are easy to fill out: * Required Parameters * Optional Parameters They are `charset=` of `text/html; charset=utf-8`, for example. Nothing available for MessagePack. They're N/A. * Fragment Identifier...

The other forms are more complex. * Security Considerations [JSON says](https://tools.ietf.org/html/rfc7159#section-12): > it is possible to use that language's "eval()" function to parse JSON texts. This generally constitutes an unacceptable...

* Application Usage [An existent mime type just says "Various"](https://www.iana.org/assignments/media-types/application/vnd.api+json) but it should be more specific to aim at standard tree, I think. [JSON says a good example](https://www.iana.org/assignments/media-types/application/json): > JSON...

@mnot Thank you for the comments & actions. * Certainly `application/msgpack` is the media type we would like to use: Reasons why we currently use `application/x-msgpack` is that `application/msgpack` is...

A solution is adding an error handler to PackerConfig and MessagePacker calls it with the BigInteger and MessagePacker instance. The default handler will throw IllegalArgumentException. Users may set other handlers...

```java public class MessagePack { public interface IllegalBigIntegerHandler { void handle(MessagePacker packer, BigInteger bi); } public static class PackerConfig { ... private IllegalBigIntegerHandler = (packer, bi) -> { throw new...