From 0b3a4aeb5ce1bb3894855f8494b8ceaa859efcd5 Mon Sep 17 00:00:00 2001 From: Ivan FB Date: Wed, 29 Apr 2026 18:25:42 +0200 Subject: [PATCH] extend SDS component definition --- standards/application/reliable-channel-api.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/standards/application/reliable-channel-api.md b/standards/application/reliable-channel-api.md index 25683c2..84f4530 100644 --- a/standards/application/reliable-channel-api.md +++ b/standards/application/reliable-channel-api.md @@ -106,7 +106,8 @@ See [SEGMENTATION](./segmentation.md). - Each new segment to be sent, requires the following data: - `MessageId`: a 40-character random hex string (e.g. `a23f89b4df7e1ba5a709352da3a247a4fd609f4c`), generated by the Reliable Channel API. - `ChannelId`: the `channelId` passed to `createReliableChannel`. - - Retrieval hint: the transport `MessageHash` of the segment, exposed by the underlying [MESSAGING-API](/standards/application/messaging-api.md). The hint provider registered during [Node initialization](#node-initialization) performs this `MessageId → MessageHash` lookup. + - Retrieval hint: the transport `MessageHash` of previous segments, exposed by the underlying [MESSAGING-API](/standards/application/messaging-api.md) upon ``MessageSendPropagatedEvent` reception. + The hint provider registered during [Node initialization](#node-initialization) performs this `MessageId → MessageHash` lookup. In turn, that mapping MUST be persisted by SDS using the `persistence` backend configured in `SdsConfig`. - Each sent segment is registered in an outgoing buffer. - The recipient sends acknowledgements back to the sender upon receiving segments.