Closed dmcgowan closed 9 years ago
Is there a pointer to discussion on the design here? Particularly how about handling other codecs such as protobuf, etc which I believe was a design goal of beam/libchan. Should the encoding mechanism not be generic and not tied to the msgpack format?
Yes, msgpack usage is described in the PROTOCOL file. Any discussion about the protocol has been in irc. Comments welcome! The goal is to have channels only use one serialization method, byte streams are anything goes since libchan defines no restrictions.
Added support to Message object to support encoding and decoding the data using msgpack. This change represents the smallest number of changes to the interface to support msgpack and update Message to use a ReadWriteCloser instead of an os file.
This is only the first phase of a larger change to support sending and receiving dynamic types.