Derek McGowan

@stevvooe in the case of msgpack, omitting a nil pointer should really be done by annotation flags rather than assuming a nil pointer will not serialize. In msgpack nil is...

@mcollina I think it is fair to document how NULL is expected to be used. I think in Go using NULL will be natural, but if it shows up on...

Using raw message does not need to change any of the types. I was mentioning using it for decoding, not encoding. When sending a message which could have multiple types,...

There might be some overlap here with the proposal for logging and debugging but worth keeping separate. I think as we get closer to moving libchan into other projects this...

My thoughts on this and general synchronization is mostly about how acks would need to work. To get normal channel behavior (without select), a single ack is needed to be...

I like it, I think we are on the same page that the best way to solve pub/sub is through an attached service. Thanks for linking. It is probably a...

There has already been some discussion over this for libchan in general in #21. Currently there are no plans to expand the official protocol to support a wire protocol other...

Agreed about ease of implementation, SPDY isn't the easiest protocol to implement. The attraction of SPDY is more that there is a defined standard and it has been proven effective....

I can speak to the spdy transport implementation, since that will be default it may make sense to make its semantics the standard for the protocol in the future. In...

@pkieltyka the plan is to track spdy which is tracking http/2. Spdy/4 should be compatible with http/2 and allow us to use a standard go implementation. Http/2 does have quite...