Tim
Tim
That's correct.
The default thread pool is configured [here](https://github.com/google/tarpc/blob/92f157206d68f75d64cf3e37808e517481fe648b/src/sync/server.rs#L29). It's entirely configurable, so you can specify the options that work best for your use case.
Is there anything else you feel is unresolved with this?
Hey, thanks for this question! So I don't have an official answer to this, but it's an area of interest, and I have a proof of concept for how one...
Thanks for the feedback! As I mentioned above, this is still an area of exploration. If you're looking for a ready to use RPC server that can run on one...
Thank you for this example! I'll dig into it soon.
@omac777 thank you for the examples! Do you happen to have a git repo you're working in? It might be illuminating if I could look at diffs between what worked...
I just looked a bit more closely at the first error you posted above. ``` error: parenthesized type parameters may only be used with a `Fn` trait --> tarpc/examples/rs-mfw-tarpc-serviceregistry.rs:319:37 |...
I'm glad you got it to work! Can I ask your opinion on the "registry" style service? Is it better than nothing? If you think it's usable, I could publish...
Hey, thanks for the question! Tarpc in its latest iteration is generic over the transport layer. My expectation is you should be able to wrap your transport in a TLS...