Expand description
§JSON-RPC for Embedded Systems
This crate provides a JSON-RPC server implementation for embedded systems.
§Features
#![no_std]Support: Fully compatible with environments lacking a standard library.- Predictable Memory Usage: Zero dynamic allocation with statically sized buffers.
- Async: Non-blocking I/O with
embedded-io-async. - Client Compatibility: Uses LSP style framing for JSON-RPC messages.
- Error Handling: Adheres to JSON-RPC standards with robust error reporting.
§Example Usage
use embedded_jsonrpc::{RpcError, RpcResponse, RpcServer, RpcHandler, JSONRPC_VERSION, DEFAULT_HANDLER_STACK_SIZE};
use embedded_jsonrpc::stackfuture::StackFuture;
use embedded_io_async::{Read, Write, ErrorType};
struct MyStream;
impl ErrorType for MyStream {
type Error = embedded_io_async::ErrorKind;
}
impl Read for MyStream {
async fn read(&mut self, buf: &mut [u8]) -> Result<usize, Self::Error> {
Ok(0)
}
}
impl Write for MyStream {
async fn write(&mut self, buf: &[u8]) -> Result<usize, Self::Error> {
Ok(0)
}
}
struct MyHandler;
impl RpcHandler for MyHandler {
fn handle<'a>(&self, id: Option<u64>, _method: &'a str, _request_json: &'a [u8], response_json: &'a mut [u8]) -> StackFuture<'a, Result<usize, RpcError>, DEFAULT_HANDLER_STACK_SIZE> {
StackFuture::from(async move {
let response: RpcResponse<'static, ()> = RpcResponse {
jsonrpc: JSONRPC_VERSION,
error: None,
result: None,
id,
};
Ok(serde_json_core::to_slice(&response, response_json).unwrap())
})
}
}
async fn serve_requests() {
let mut server: RpcServer<'_, MyStream> = RpcServer::new();
server.register_handler("echo", &MyHandler);
loop {
let mut stream: MyStream = MyStream;
server.serve(&mut stream).await.unwrap();
}
}§License
This crate is licensed under the Mozilla Public License 2.0 (MPL-2.0). See the LICENSE file for more details.
§References
Modules§
- This crate defines a
StackFuturewrapper around futures that stores the wrapped future in space provided by the caller. This can be used to emulate dyn async traits without requiring heap allocation.
Structs§
- JSON-RPC Error structure
- JSON-RPC Request structure
- JSON-RPC Response structure
- RPC server
Enums§
- JSON-RPC Standard Error Codes
- Type for errors returned by the RPC server
Constants§
- Default stack size for futures. This is a rough estimate and will need to be adjusted based on the complexity of your handlers.
- Default handler timeout in milliseconds. This is the maximum time allowed for a handler to process a request.
- Default maximum number of clients.
- Maximum number of registered RPC methods.
- Maximum length of a JSON-RPC message (including headers). Default to the largest message that’ll fit in a single Ethernet frame.
- Default notification queue size. This is the maximum number of notifications that can be queued for sending.
- Default write timeout in milliseconds. This is the maximum time allowed for writing to the stream.
- JSON-RPC Version Currently only supports version 2.0 https://www.jsonrpc.org/specification
Traits§
- Trait for RPC handlers TODO: when async closures are stabilized, we should offer a way to register closures directly.