docker/libchan

Dual transport

dmcgowan opened this issue · 2 comments

The default SpdyTransport uses spdy streams for messages as well as byte streams. A Dual transport would allow for using spdy streams for messages, but a different network type for byte streams. This would most likely involve adding a transport type which is created with a network connection for channels over spdy, but contains a listener/dialer for creation of byte streams. This would allow calls to CreateByteStream on the transport's sender to return real network connections. Any new protocol should be clearly defined and referenced by changes to the Protocol document to ensure different implementation of libchan are in agreement of the transport protocol.

I think this ties into what we have run into over at jschan: GraftJS/jschan#22

Stream level abstraction in 0.2.0 makes this a possibility without changing the core network libchan implemenation.