Consider the following situation:
- server is Rust/x86_64
- client is Rust/wasm32
- they are talking over websocket
Is there a standard crate / library for doing RPC in this environment ? I would prefer a solution where both Rust/x86_64 and Rust/wasm32 can server as the "rpc server" and the "rpc client"
I'm not aware of any RPC library for this situation.
Is a reasonable chain of logic something like this: when someone sets out to write a RPC, they probably want to use some known standard, so they pick Thrift or gRPC. Then they want it to be high performance, so they go with async io / tokio. Therefore, all RPC libraries "converge" towards being Thrift / gRPC on tokio?
Well, you kinda need a standard for the protocol before it makes sense to build a large RPC library for the protocol.
This topic was automatically closed 90 days after the last reply. We invite you to open a new topic if you have further questions or comments.