libchan
libchan copied to clipboard
docker
Like Go channels over the network
Libchan can be difficult to debug network interactions through traditional packet sniffing. Because of the lack of tooling which currently exists around debugging spdy, libchan should have a debug mechanism...
Implement the stream provider interface with an SSH connection
I'm starting to work on a node.js / javascript implementation using streams as the base abstraction (less elegant than goroutines, but I can see them working). Other than the websocket...
Add support for encoding and decoding Go channels using the channel extended type with the new msgpack library.
Most of the power of Go channels come from flexibility provided by select clauses and the analogous `reflect` package API. An efficient select functionality in `libchan` would bring it further...
Following on from #22 and #26: I think we need to define the channel semantics. Saying "the ordering depends on the underlying transport you use" isn't helpful for developers who...
In libchan we need a way to seamlessly carry trace, debugging, cancellation and other data across boundaries - whether that be process, goroutine or RPC. The code.google.com/p/go.net/context package provides wiring...
After seen the work done in #61 and #63, I think it's worth linking in here that I created a Graft/jschan pubsub broker: https://github.com/GraftJS/graft-broker. Graft-broker can also be backed by...
Add an example which demonstrates libchan being used over a websocket. Since the spdy protocol is separated from the transport, this should be possible to implement using the existing code....