logos-messaging/specs
1
0
Fork 0
mirror of https://github.com/logos-messaging/specs.git synced 2026-05-18 11:00:04 +00:00
Code Issues Packages Projects Releases Wiki Activity

MessageSentEvent is the one that confirms a msg was rx by a store node

Browse Source
This commit is contained in:
Ivan FB 2026-04-30 00:31:17 +02:00
parent f9c04366c5
commit 01cf30d5e8
No known key found for this signature in database
GPG Key ID: DF0C67A04C543270
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
standards/application/reliable-channel-api.md
View File

@ -106,7 +106,7 @@ 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 previous segments, exposed by the underlying [MESSAGING-API](/standards/application/messaging-api.md) upon ``MessageSendPropagatedEvent` reception.
- Retrieval hint: the transport `MessageHash` of previous segments, exposed by the underlying [MESSAGING-API](/standards/application/messaging-api.md) upon ``MessageSentEvent` 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.