ajj 0.6.2

Simple, modern, ergonomic JSON-RPC 2.0 router built with tower and axum
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77

//! Basic example of running a JSON-RPC server over IPC using ajj
//!
//! This example demonstrates how to set up a simple IPC server using `ajj`, and
//! defines a few basic RPC methods.
//!
//! The `make_router` function sets up a router with three routes:
//! - `helloWorld`: Returns a greeting string.
//! - `addNumbers`: Takes two numbers as parameters and returns their sum.
//! - `notify`: Sends a notification after a short delay, demonstrating the use
//!   of notifications in the RPC context.

use ajj::{
    pubsub::{
        ipc::{to_name, ListenerOptions},
        Connect,
    },
    HandlerCtx, Router,
};
use tempfile::NamedTempFile;

#[tokio::main]
async fn main() -> eyre::Result<()> {
    let router = make_router();

    // Create a temporary file for the IPC socket.
    let tempfile = NamedTempFile::new()?;
    let name = to_name(tempfile.path().as_os_str()).expect("invalid name");

    println!("Serving IPC on socket: {:?}", tempfile.path());
    println!("use Ctrl-C to stop");

    // The guard keeps the server running until dropped.
    let guard = ListenerOptions::new().name(name).serve(router).await?;

    // Shut down on Ctrl-C
    tokio::signal::ctrl_c().await?;
    drop(guard);

    Ok(())
}

// Setting up an AJJ router is easy and fun!
fn make_router() -> Router<()> {
    Router::<()>::new()
        .route("helloWorld", || async {
            tracing::info!("serving hello world");
            Ok::<_, ()>("Hello, world!")
        })
        .route("addNumbers", |(a, b): (u32, u32)| async move {
            tracing::info!("serving addNumbers");
            Ok::<_, ()>(a + b)
        })
        .route("notify", |ctx: HandlerCtx| async move {
            // Check if notifications are enabled for the connection.
            if !ctx.notifications_enabled() {
                // This error will appear in the ResponsePayload's `data` field.
                return Err("notifications are disabled");
            }

            let req_id = 15u8;

            // Spawn a task to send the notification after a short delay.
            ctx.spawn_with_ctx(|ctx| async move {
                // something expensive goes here
                let result = 100_000_000;
                let _ = ctx
                    .notify(&serde_json::json!({
                      "req_id": req_id,
                      "result": result,
                    }))
                    .await;
            });

            // Return the request ID immediately.
            Ok(req_id)
        })
}