Tim Kuehn d0d65c413a Make Client Send again (and Clone too!). ...

The basic strategy is to start a reactor on a dedicated thread running a request stream.
Requests are spawned onto the reactor, allowing multiple requests to be
processed concurrently. For example, if you clone the client to make requests
from multiple threads, they won't have to wait for each others'
requests to complete before theirs start being sent out.

Also, client rpcs only take &self now, which was also required for
clients to be usable in a service.

Also added a test to prevent regressions.

2017-03-06 21:12:44 -08:00

..

concurrency.rs

Add server::Handle::shutdown (#117)

2017-03-06 20:57:12 -08:00

pubsub.rs

Add server::Handle::shutdown (#117)

2017-03-06 20:57:12 -08:00

readme_errors.rs

Make Client Send again (and Clone too!).

2017-03-06 21:12:44 -08:00

readme_futures.rs

Add server::Handle::shutdown (#117)

2017-03-06 20:57:12 -08:00

readme_sync.rs

Make Client Send again (and Clone too!).

2017-03-06 21:12:44 -08:00

server_calling_server.rs

Add server::Handle::shutdown (#117)

2017-03-06 20:57:12 -08:00

sync_server_calling_server.rs

Make Client Send again (and Clone too!).

2017-03-06 21:12:44 -08:00

throughput.rs

Make Client Send again (and Clone too!).

2017-03-06 21:12:44 -08:00

two_clients.rs

Make Client Send again (and Clone too!).

2017-03-06 21:12:44 -08:00