Node API for read+write? about mpack HOT 1 CLOSED

Thanks, I'm glad you like MPack.

There isn't currently a standard schema for MessagePack. I have no plans to come up with one myself. There has been a bit of discussion about this on the MessagePack spec here: msgpack/msgpack#202

One of the things I like about MessagePack is that it isn't defined by a schema. I think most users of MessagePack agree. Yes, it would be powerful if you could generate the write and expect code for your structures based on a schema, but I'm not a big fan of generated code. I definitely don't want to do a dynamic schema at runtime either (it sounds like this is what you were suggesting, an API for building the schema at runtime rather than a language or file format for generated code.) I'm also not a fan of reflection or annotations or other means of mapping structures for serialization. I've thought about this a lot and I don't see how to avoid all the things I dislike about Protocol Buffers and friends, or of the various object-relation mapping tools I've used. I would rather just write the serialization code manually.

There are plenty of schema-based formats you can use for data serialization if that's what you want: Protocol Buffers, Cap'N'Proto, Amazon Ion, etc. You can always use one of those instead.

from mpack.