- Create docs/architecture/event-targets/ with individual specs: in-process, redis, websocket-client, websocket-server, worker, iroh-spoke, iroh-hub - Update event-targets.md to serve as index with topology model (symmetric vs fan-out) and adapter status table - Update architecture.md index to reference new directory
2.5 KiB
2.5 KiB
status, last_updated
| status | last_updated |
|---|---|
| draft | 2026-05-07 |
Iroh Spoke Event Target
Import: @alkdev/pubsub/event-target-iroh-spoke
Peer dep: @rayhanadev/iroh (optional, NAPI-RS native addon)
Status: Not yet implemented. Needs R&D on binding stability and Deno/NAPI compatibility.
P2P QUIC event target for the spoke (client) side. The spoke initiates the connection and opens the bidirectional stream.
createIrohSpokeEventTarget
async function createIrohSpokeEventTarget<TEvent extends TypedEvent>(
args: CreateIrohSpokeEventTargetArgs,
): Promise<TypedEventTarget<TEvent>>;
CreateIrohSpokeEventTargetArgs
| Field | Type | Required | Description |
|---|---|---|---|
endpoint |
Endpoint |
Yes | iroh endpoint (created with Endpoint.create()) |
hubNodeId |
string | NodeId |
Yes | The hub's public key (Ed25519) |
alpn |
string |
No | Application-layer protocol. Default: "alkpubsub/1" |
Protocol
Single bidirectional QUIC stream per connection. Length-prefixed JSON messages:
[4 bytes: length N][N bytes: JSON payload]
The JSON payload is the EventEnvelope:
{ "type": "call.responded", "id": "uuid-123", "payload": { "output": 42 } }
Connection Flow
- Spoke creates
Endpoint - Spoke calls
endpoint.connect(hubNodeId, alpn)→Connection - Spoke calls
connection.openBi()→SendStream+RecvStream - Spoke wraps streams in
IrohSpokeEventTarget - On disconnect:
RecvStream.readExact()throws, spoke must reconnect
Key Properties
- NAT traversal — spoke dials hub by
NodeId, no public IP needed - Cryptographic identity —
Connection.remoteNodeId()verifies the hub - Bidirectional —
dispatchEventwrites toSendStream,addEventListenerreads fromRecvStream - Per-connection — one event target per QUIC connection
R&D Needed
- Binding stability —
@rayhanadev/irohhas one author and no tests. API surface is small (10 methods) but needs validation. - NAPI under Deno — NAPI-RS
.nodebinaries need testing under Deno 2.x. - Stream multiplexing — multiple
openBi()streams on one connection vs. single stream with multiplexed events. Single stream + JSON framing is simpler. - Reconnection —
RecvStream.readExact()throws on connection close. Need to propagate this to listeners and support reconnect.
See ../iroh-transport.md for full protocol details, identity, and comparison with WebSocket.