Or maybe I have just greatly misunderstood how to use the library. Any input is greatly appreciated! :)

Hey, thanks for the interest! Quick plug of our discord channel, which is good for longer-form discussions.

• Re: [1], tarpc is transport agnostic, so you are free to plug in whatever transport you're using. Ultimately you just need something that impls Stream<Item = io::Result<tarpc::ClientMessage<Request>>> + Sink<tarpc::Response<Response>, Error = io::Error> that you can pass to BaseChannel::new.
• Re: [2], your server.await only waits until the stream of incoming connections is closed. Handler::respond_with spawns each channel onto the tokio default executor. Once the channels are spawned, the executor still needs to execute them. But since you only have one client, I would entirely avoid using server::new, which is really just a small shim to help serve a stream of channels. Channel represents a server connection to a client and can be used by itself (see above bullet).

Try this:

BaseChannel::with_defaults(server_transport)
    .respond_with(HelloServer(client_addr).serve())
    .execute()
    .await;

By the way, I'd appreciate any PRs to make the documentation more helpful!

Awesome! Thanks. Fewer types involved and fewer hacks needed (stream::once(future::ready(server_transport))). That is indeed a cleaner way to handle a single connection. I'll try it out later. Maybe I'll come by the discord channel if I run into more problems :)

Hey @faern, anything else you need help with? Can I close this issue?

Thanks for the new example. That's awesome.

I still think there is some documentation that can be improved. But I have not had the time to play more with this since you provided additional information.

Channel::respond_with:

Respond to requests coming over the channel with f. Returns a future that drives the responses and resolves when the connection is closed.

It seems this documentation is not entirely true since the future completes before the response are fully completed? And it's not immediately clear to me that "connection is closed" refers to the listening server socket and not all the client sockets.

The discord invite does not work. Maybe it expired or I'm not good enough at understanding discord 😅

Do you link to the discord anywhere except randomly in issues? It's not in the main readme. It would be a great way to find the community.

There's a discord badge in the readme 🙂

And it's not immediately clear to me that "connection is closed" refers to the listening server socket and not all the client sockets.

This refers to the one client connection managed by the channel. It does not refer to a server listening on a socket.

Thanks! Badges does not work for ctrl-f disco..., chat or community :D

This refers to the one client connection managed by the channel. It does not refer to a server listening on a socket.

But you just said the opposite:

your server.await only waits until the stream of incoming connections is closed

.. Or I'm too tired :D

I think the confusion is that there are multiple respond_with fns, one on Channel and one on server.incoming(). The one on server.incoming() is the one that only waits until server.incoming() is closed.