A general-purpose, batteries-included JSON-RPC 2.0 router, inspired by axum's routing system.
ajj aims to provide simple, flexible, and ergonomic routing for JSON-RPC.
- Copy-free routing of JSON-RPC requests to method handlers.
- No-boilerplate method handlers. Just write an async function.
- Support for pubsub-style notifications.
- Built-in support for axum, and tower's middleware and service ecosystem.
- Basic built-in pubsub server implementations for WS and IPC.
- A Handler is a function that processes some JSON input, and succeeds or fails with some data.
- A Method is a handler with an associated name, which is used by the incoming request to identify a specific Handler.
- A Router is a collection of Methods.
- A Server exposes a Router over some transport.
See the crate documentation on docs.rs for more detailed examples.
use ajj::{Router};
// Provide methods called "double" and "add" to the router.
let router = Router::<u64>::new()
// "double" returns the double of the request's parameter.
.route("double", |params: u64| async move {
Ok::<_, ()>(params * 2)
})
// "add" returns the sum of the request's parameters and the router's stored
// state.
.route("add", |params: u64, state: u64| async move {
Ok::<_, ()>(params + state)
})
// The router is provided with state, and is now ready to handle requests.
.with_state::<()>(3u64);
axum
- implements thetower::Service
trait forRouter
, allowing it to be used as an axum handler.pubsub
- adds traits and tasks for serving the router over streaming interfaces.ws
- adds implementations of thepubsub
traits for tokio-tungstenite.ipc
- adds implementations of thepubsub
traits for interprocesslocal_sockets
.
We recommend axum for serving the router over HTTP. The Router
provides an
into_axum(path: &str)
method to instantiate a new axum::Router
, and
register the router to handle requests.
For WS and IPC connections, the pubsub
module provides implementations of the
Connect
trait for [std::net::SocketAddr
] to create simple WS servers, and
interprocess::local_socket::ListenerOptions
to create simple IPC servers.
Users with more complex needs should provide their own Connect
implementations.
See the crate documentation on docs.rs for more detailed examples.
Some code in this project has been reproduced or adapted from other projects. Files containing that code contain a note at the bottom of the file indicating the original source, and containing relevant license information. Code has been reproduced from the following projects, and we are grateful for their work: