Server acting as a client to another server about tarpc HOT 5 CLOSED

Hi! I think the pubsub example does something like this: see async fn publish

I'd also be happy to take a look at your code, if you can point me to it!

from tarpc.

Ah, yes, that is correct! #[tarpc::server] is an optional attribute that hides some of the boilerplate of defining the Future associated types and such.

from tarpc.

Thanks! Let me take a look at the publish function first and I'll get back to you.

from tarpc.

Hi @tikue, I have another similar question. I have declared my functions similarly to readme.rs where in the trait they are declared as async but in the implementation, they are not. When I put the async keyword in the implementation (like line 31 in front of fn hello(...) I get the following error:

expected struct `futures::future::Ready`, found opaque type`

The "opaque type" is Ready<String>.

Here is the example from readme.rs. If you uncomment line 34 it throws the above error.

from tarpc.

Okay, I think I figured it out. So, after adding the #[tarpc::server] and the async keyword, I had to completely remove the Futures. Now it works fine. Does the #[tarpc::server] automatically translate the return types to futures?

from tarpc.