Tim

Nope, I've been pretty busy with work/life the last few months and haven't been actively developing new features. I'd be happy to mentor on this or any other feature request.

With #199, this can be implemented in the transport layer. However, I think this could also be done at a higher level of abstraction. I'm imagining some kind of load...

The field `client::Config.pending_request_buffer` controls how large the `Sink` can grow. When it reaches capacity, the response Future will remain in a pending state until there's room to add the request...

Rather than calling `incoming.respond_with()` do `incoming.for_each(|channel| channel.respond_with())`. That gives you a chance to take the peer addr from the channel. Something like this (modified README example): ```rust #[derive(Clone)] struct HelloServer(SocketAddr);...

@omac777 was your question answered?

Thanks for the PR and for your patience with my review! Looks like there's a test failure: 

This was obsoleted by #380. Thank you for the contribution, and I'm sorry we couldn't get this one merged!

Hi @ywww sorry, I must have missed this! I don't have any experience with socks5 proxies, could you clarify the question? Do you want to run a tarpc service on...

Strangely, I'm not able to reproduce this. Can you provide the exact code that causes this to occur?

@schoeppl I cloned your tarpctest repo and now am hitting this problem, which makes me think this is some kind of rustc cross-crate bug. Will file an issue upstream.