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

consistency changes

Browse Source
This commit is contained in:
Ivan FB 2026-04-24 09:32:35 +02:00
parent f5b1199a87
commit 706fa664d1
No known key found for this signature in database
GPG Key ID: DF0C67A04C543270
1 changed files with 5 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -212,7 +212,7 @@ types:
type: ReliableEnvelope type: ReliableEnvelope
description: "The reassembled message and its channel context. `envelope.messageEnvelope.payload` contains the fully reassembled content; `envelope.channelId` identifies the channel on which it arrived." description: "The reassembled message and its channel context. `envelope.messageEnvelope.payload` contains the fully reassembled content; `envelope.channelId` identifies the channel on which it arrived."
EventReliableMessageSent: EventMessageSent:
type: object type: object
description: "Event emitted when all chunks of a message have been acknowledged by the network." description: "Event emitted when all chunks of a message have been acknowledged by the network."
fields: fields:
@ -277,7 +277,7 @@ Each `ReliableChannel` MUST maintain internal state for [SDS](https://lip.logos.
- An outgoing buffer of unacknowledged message chunks pending confirmation. - An outgoing buffer of unacknowledged message chunks pending confirmation.
- An incoming buffer for partially received segmented messages awaiting full reassembly. - An incoming buffer for partially received segmented messages awaiting full reassembly.
The state MUST be persisted using to the `persistence` tool specified in `SdsConfig`. The state MUST be persisted using the `persistence` backend specified in `SdsConfig`.
The default `memory` backend does not survive process restarts; implementors providing persistence SHOULD use a durable backend. The default `memory` backend does not survive process restarts; implementors providing persistence SHOULD use a durable backend.
**Encryption**: **Encryption**:
@ -311,7 +311,8 @@ When `send` is called with a `ReliableEnvelope` whose `channelId` is non-empty,
1. **Segment**: Split the payload into chunks as defined in [SEGMENTATION-API](./segmentation-api.md). 1. **Segment**: Split the payload into chunks as defined in [SEGMENTATION-API](./segmentation-api.md).
2. **Apply [SDS](https://lip.logos.co/ift-ts/raw/sds.html)**: Register each chunk with the SDS layer to track acknowledgements and enable retransmission. 2. **Apply [SDS](https://lip.logos.co/ift-ts/raw/sds.html)**: Register each chunk with the SDS layer to track acknowledgements and enable retransmission.
3. **Encrypt**: If an `IEncryption` implementation is provided, encrypt each chunk before transmission. 3. **Encrypt**: If an `IEncryption` implementation is provided, encrypt each chunk before transmission.
4. **Dispatch**: Send each chunk via the underlying [MESSAGING-API](/standards/application/messaging-api.md). 4. **Rate Limit**: If `RateLimitConfig.enabled` is `true`, delay dispatch as needed to comply with [RLN](https://lip.logos.co/messaging/standards/core/17/rln-relay.html) epoch constraints.
5. **Dispatch**: Send each chunk via the underlying [MESSAGING-API](/standards/application/messaging-api.md).
**Incoming message processing order**: **Incoming message processing order**:
@ -348,7 +349,7 @@ See [SEGMENTATION-API](./segmentation-api.md).
- The recipient sends acknowledgements back to the sender upon receiving chunks. - The recipient sends acknowledgements back to the sender upon receiving chunks.
- The sender removes acknowledged chunks from the outgoing buffer. - The sender removes acknowledged chunks from the outgoing buffer.
- Unacknowledged chunks are retransmitted after `acknowledgementTimeoutMs`. - Unacknowledged chunks are retransmitted after `acknowledgementTimeoutMs`.
- SDS state MUST be persisted in the configured `historyBackend`. - SDS state MUST be persisted using the `persistence` backend configured in `SdsConfig`.
### Rate Limit Manager ### Rate Limit Manager