Łukasz Kurowski

@hugues31 I believe we should focus on creating a boilerplate code to be used in #47.

I have implemented [Poloniex](https://github.com/crypto-bank/orca/blob/87b2aa6360a9b57ae8d8651e42cd7791e9edef0d/clients/src/poloniex/stream.rs) websocket stream. I would like to discuss moving some code out of [orca](https://github.com/crypto-bank/orca) to coinnect, it doesn't make much of a sense to maintain two clients....

I think I have completed the interface for websockets. I made sure that implementation of new websocket [protocols](https://github.com/crypto-bank/orca/blob/master/orca/streams/poloniex/mod.rs) is as simple as possible. Poloniex is stable and tested, for now...

I am not entirely happy with [this](https://github.com/crypto-bank/crypto-market-stream-poloniex/blob/master/examples/poloniex-stream.rs) interface, but it works. Some things I do not like in my current implementation * ~commands should be possible to receive again on...

I was also interested in running OCI built with `dgr` mainly because of `runc` startup speed (can rkt be as fast?). I found [aci2oci](https://github.com/liangchenye/aci2oci) converter but did not test it.

What is the benefit of returning `Result` as opposed to a `Future`? I can't see any, more than that - I see it as harmful for the interfaces - `ServiceAsync`?...

> error type coercion could be defined and then used in handlers for better error handling and propagation. I am not sure I understand but futures are defined as `Future`...

@st33l have the same problem, I'm running BackTrack 5 RC 3. ``` torproxy 0.3 by Moxie Marlinspike. Retrieving directory listing... Added: x.x.x.x (24 more...) Added: x.x.x.x Segmentation fault ```

Im not sure but it may be a directory listings protocol incompatibility.

When i built @manurautela solution it still wasn't working on some directory listings.