- jsChan [https://github.com/graftjs/jschan https://github.com/graftjs/jschan]. Our javascript implementation of Docker's libchan library. It implements the sa

- jsChan [https://github.com/graftjs/jschan https://github.com/graftjs/jschan]. Our javascript implementation of Docker's libchan library. It implements the same kind of semantics that Go channels have, but over the network, and using node streams. Since it is based on the capabilities of SPDY, it allows you to embed additional channels in messages. So i could request a page, but give you a return channel to write the document to. instead of waiting for the response. - Graft [https://github.com/graftjs/graft https://github.com/graftjs/graft]. Our attempt to determine what microservices taken all the way to the browser would look like. It's a higher level library built on top of jschan. The idea is to be able to use node streams interchangeably on both sides of the pipe, with the communication managed by libchan ... and work invisibly over SPDY or websockets or whatever. Unfortunately, SPDY was replaced by http2, which meant that libchan went under construction for a bit while the library support was figured out. At the same time, io.js happened. And now there's a very fastly evolving streams spec that is feeding on the whatwg effort to standardise a stream spec for the browser and node. I am going to take up the mantle again, but there needs to be some settling of the ecosystem first. =\