This is a simple rpc library inspired by server_fn
from the leptos
ecosystem. It allows you to define functions the will be run on a server, but
called from client. The primary usecase is webapps with a rust frontend, but
the library is designed to be easily adapatable and places no restrictions on
transport protocol or serialization format.
ClientRpcService::handle
on the client and
handle_rpc
on the server to control how rpc calls reaches the server and
responses back.marpc
also defines a simple json
format that you can use.Start by defining a rpc service:
```rust struct Service;
impl marpc::RpcService for Service { type Format = marpc::Json; }
impl marpc::ClientRpcService for Service {
type ClientError = Box
fn handle<'a>(
uri: &'static str,
payload: &'a [u8],
) -> Pin<Box<dyn 'a + Future<Output = Result<Vec<u8>, Self::ClientError>>>> {
// Send payload to the server
}
}
marpc::register_service!(Service); ```
Define rpc functions with the following:
```rust
async fn add(a: i32, b: i32) -> Result And call them on the client with: On the server you can handle rpc calls with: See See This library is dual-licensed under the MIT license and Apache License 2.0.
Chose the license to use at your own discretion. See
LICENSE-MIT and LICENSE-APACHE.rust
add(5, 6).await;
rust
marpc::handle_rpc::<Service>(uri, (), payload).await
examples/add.rs
for a simple example of two threads
communicating over a global queue. Note that this must be compiled with
--all-features
or --features client,server
as both the client and server
code needs to be generated.examples/hello_net.rs
for a more sophisticated
example with a client and server communicating over a tcp stream. Run
cargo run --features server --example hello_net -- server Hello
in one window
and then open another window and run
cargo run --features client --example hello_net -- client world
.License