From 8d114a1285a107e5da44dec5a7a6a0d865d1f20a Mon Sep 17 00:00:00 2001 From: nvms Date: Fri, 18 Apr 2025 07:59:58 -0400 Subject: [PATCH] README --- packages/mesh/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/packages/mesh/README.md b/packages/mesh/README.md index 6d46c3c..cf00381 100644 --- a/packages/mesh/README.md +++ b/packages/mesh/README.md @@ -357,7 +357,7 @@ await client.unsubscribeRecord("product:456"); ### Versioning and Resync -Every update includes a `version`. Clients should track the current version and, in `patch` mode, expect `version === localVersion + 1`. If a gap is detected (missed patch), the client will automatically be sent a full record update to resync. +Every update includes a `version`. Clients track the current version and, in `patch` mode, expect `version === localVersion + 1`. If a gap is detected (missed patch), the client will automatically be sent a full record update to resync. It does this by transparently unsubscribing and resubscribing to the record. This system allows fine-grained, real-time synchronization of distributed state with minimal overhead. @@ -418,7 +418,7 @@ Middleware functions receive the same `MeshContext` object as command handlers a Mesh includes a built-in ping/pong system to track latency and detect dead connections. This is implemented at the _application level_ (not via raw WebSocket protocol `ping()` frames) to allow for: -- Accurate latency measurement from server to client. +- Accurate round-trip latency measurement from server to client. - Graceful connection closure and multi-instance Redis cleanup. - Fine-tuned control using configurable missed ping/pong thresholds.