Tim Kuehn fe20c8af14 Add a reactor::Core field to SyncClient. ...

This allows the client to drive its own execution, as one would expect.
Previously, the reactor had to be driven on a separate thread, which was confusing.
This has a couple notable side effects:
  1. SyncClient is no longer `Clone`.  This is because `reactor::Core`
     is not `Clone`, and creating one is not infallible
     (`Core::new` returns a `Result`).
  2. SyncClient does not use the user-specified `client::Options::handle` or
     `client::Options::remote`, because it constructs its own reactor.

2017-02-01 22:32:25 -08:00

..

concurrency.rs

Cargo clippy

2017-01-22 21:16:11 -08:00

pubsub.rs

Add a reactor::Core field to SyncClient.

2017-02-01 22:32:25 -08:00

readme_errors.rs

Add a reactor::Core field to SyncClient.

2017-02-01 22:32:25 -08:00

readme_futures.rs

Add Options to all connect and listen fns

2017-01-12 00:06:17 -08:00

readme_sync.rs

Add a reactor::Core field to SyncClient.

2017-02-01 22:32:25 -08:00

server_calling_server.rs

Add a reactor::Core field to SyncClient.

2017-02-01 22:32:25 -08:00

throughput.rs

Add a reactor::Core field to SyncClient.

2017-02-01 22:32:25 -08:00

two_clients.rs

Add a reactor::Core field to SyncClient.

2017-02-01 22:32:25 -08:00