Expand description
§Transport agnostic jsonrpc library.
Right now it supports only server side handling requests.
use tetsy_jsonrpc_core::*;
use tetsy_jsonrpc_core::futures::Future;
fn main() {
let mut io = IoHandler::new();
io.add_method("say_hello", |_| {
Ok(Value::String("Hello World!".into()))
});
let request = r#"{"jsonrpc": "2.0", "method": "say_hello", "params": [42, 23], "id": 1}"#;
let response = r#"{"jsonrpc":"2.0","result":"Hello World!","id":1}"#;
assert_eq!(io.handle_request(request).wait().unwrap(), Some(response.to_string()));
}
Re-exports§
pub use crate::delegates::IoDelegate;
pub use crate::middleware::Middleware;
pub use crate::middleware::Noop as NoopMiddleware;
pub use futures;
pub use crate::types::*;
Modules§
- delegates
- Delegate rpc calls
- middleware
IoHandler
middlewares- types
- JSON-RPC types
Structs§
- IoHandler
- Simplified
IoHandler
with noMetadata
associated with each request. - Meta
IoHandler - Request handler
Enums§
- Compatibility
IoHandler
json-rpc protocol compatibility- Remote
Procedure - Possible Remote Procedures with Metadata
Traits§
- IoHandler
Extension - A type that can augment
MetaIoHandler
. - Metadata
- Metadata trait
- RpcMethod
- Asynchronous Method with Metadata
- RpcMethod
Simple - Asynchronous Method
- RpcNotification
- Notification with Metadata
- RpcNotification
Simple - Notification
Functions§
- serde_
from_ str - workaround for https://github.com/serde-rs/json/issues/505 Arbitrary precision confuses serde when deserializing into untagged enums, this is a workaround
Type Aliases§
- BoxFuture
- A
Future
trait object. - Future
Output - A type representing middleware or RPC call output.
- Future
Response - A type representing middleware or RPC response before serialization.
- Future
Result - A type representing future string response.
- Future
RpcResult - A type representing an optional
Response
for RPCRequest
. - Result
- A Result type.