jerry/buzz
1
0
Fork 0
mirror of https://github.com/block/buzz.git synced 2026-11-12 20:31:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs(serverless): explain why desktop ws_pool is hand-rolled vs agent's nostr-relay-pool

Browse Source
This commit is contained in:
Michael Neale
2026-06-03 15:02:38 +10:00
parent 604f5f3b2e
commit 9745e9940d
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
desktop/src-tauri/src/ws_pool.rs
View File

@@ -13,6 +13,16 @@
//! dispatches incoming messages to in-flight requests by subscription id
//! (queries) or event id (OK acks). Connections are re-established on demand
//! after a drop. NIP-42 AUTH challenges are answered automatically.
//!
//! **Why hand-rolled here, but `nostr-relay-pool` in the agent (`sprout-acp`):**
//! the standalone agent binary adopts `nostr-relay-pool` for free auto-reconnect
//! / auto-resubscribe / dedup. The desktop deliberately does NOT, to avoid
//! pulling a *second* rustls/TLS stack (`async-wsocket`) into the Tauri process,
//! which already runs aws-lc-rs rustls for reqwest/media/tungstenite — two
//! crypto providers in one process risks a `CryptoProvider` install panic. This
//! pool is serverless-only and already self-heals (drops are detected via the
//! `alive` flag and reconnected on next use), so the agent's missed-message bug
//! does not apply here.
use std::collections::HashMap;
use std::sync::Arc;