IPC Broker (Tokio-based)

A lightweight inter-process communication (IPC) broker built with Tokio and Rust. It provides RPC, publish/subscribe eventing, and supports both TCP and Unix domain sockets for Linux and macOS, and both TCP and Named Pipes for Windows.

✨ Features

• Dual transport support

  • TCP (127.0.0.1:5123)
  • Unix socket (/tmp/ipc_broker.sock)
  • Named Pipes (\\.\pipe\ipc_broker)

• RPC calls

  • Clients can call registered objects exposed by workers.
  • Responses are automatically routed back to the original caller.

• Object registration

  • Workers can register named objects.

• Pub/Sub

  • Clients can subscribe to topics and receive published events.

• Actor-based connection handling

  • Each connection runs as an async actor.
  • Read/write are decoupled through channels for maximum concurrency.

🧩 Architecture Overview

+-------------+        +-------------+        +-------------+
|   Client    | <----> |   Broker    | <----> |   Worker    |
|-------------|        |-------------|        |-------------|
| RPC calls   |        | Routes RPCs |        | Exposes RPC |
| Pub/Sub     |        | Routes Pubs |        | Handles req |
+-------------+        +-------------+        +-------------+

• Broker – Routes all communication between clients and workers.
• Worker – Registers objects and executes requested methods.
• Client – Invokes remote methods, publishes events, or subscribes to topics.

🚀 Getting Started (Development)

1. Run the Broker

cargo run --bin ipc-broker

The broker will listen on:

• TCP: 127.0.0.1:5123
• Unix socket: /tmp/ipc_broker.sock (on Linux/macOS)
• Named pipe: \\.\pipe\ipc_broker (on Windows)

2. Run a Worker

Your worker connects to the broker and registers callable objects.

Example:

use async_trait::async_trait;
use ipc_broker::worker::{SharedObject, WorkerBuilder};
use serde::{Deserialize, Serialize};
use serde_json::Value;

#[derive(Deserialize, Serialize)]
struct Args {
    a: i32,
    b: i32,
}

pub struct Calculator;
#[async_trait]
impl SharedObject for Calculator {
    async fn call(&self, method: &str, args: &Value) -> Value {
        let parsed = serde_json::from_value(args.clone());

        match (method, parsed) {
            ("add", Ok(Args { a, b })) => json!({"sum": (a + b)}),
            ("mul", Ok(Args { a, b })) => json!({"product": (a * b)}),
            (_, Err(e)) => Value::String(format!("Invalid args: {e}")),
            _ => Value::String("Unknown method".into()),
        }
    }
}

#[tokio::main]
async fn main() -> std::io::Result<()> {
    let calc = Calculator;

    WorkerBuilder::new().add("math", calc).spawn().await?;
    Ok(())
}

3. Use the rob Command-Line Tool

The rob utility is a helper CLI for interacting with the broker.

🧪 Syntax

rob <command> <object> <method> [signature] [args...]

🧪 Examples

🧩 Example 1 – RPC Call

Call a registered worker method:

rob call math add {ii} a 10 b 32

Explanation:

• {ii} means a map with keys a and b, both integers.
• The arguments a 10 b 32 correspond to the values.

Expected Output:

Result:
Map:
  sum :: 42

📢 Example 2 – Publish an Event

Publish a message to subscribers:

rob send sensor temperature s "25.6°C"

Signature s = string argument Publishes a temperature event with the value "25.6°C".

📢 Example 3 – Subscribe to a Topic

Listen for published events:

rob listen sensor temperature

Output:

Listening for: object=sensor method=temperature. Press ctrl+c to exit.

Result:
"25.6°C"

🧰 Signature Syntax Reference

Examples:

# Map example
rob call user info {i} id 123

# Array example
rob call math sum (ii) 1 2

🛠 Building

cargo build --release

The resulting binaries will be placed in target/release/.

🪟 Platform Notes

📄 License

MIT License © 2025