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

rm state management

Browse Source
This commit is contained in:
Ivan FB 2026-04-28 00:43:22 +02:00
parent 3c1125bddb
commit 198ad99bed
No known key found for this signature in database
GPG Key ID: DF0C67A04C543270
1 changed files with 0 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -18,7 +18,6 @@ editor: Logos Messaging Team
* [Architectural position](#architectural-position) * [Architectural position](#architectural-position)
* [IDL](#idl) * [IDL](#idl)
* [Procedures](#procedures) * [Procedures](#procedures)
* [State management](#state-management)
* [Outgoing message processing](#outgoing-message-processing) * [Outgoing message processing](#outgoing-message-processing)
* [Incoming message processing](#incoming-message-processing) * [Incoming message processing](#incoming-message-processing)
* [Retransmission](#retransmission) * [Retransmission](#retransmission)
@ -97,15 +96,6 @@ A custom Interface Definition Language (IDL) in YAML is used, consistent with [M
## Procedures ## Procedures
### State management
Each `ReliableChannel` MUST maintain internal state for [SDS](https://lip.logos.co/ift-ts/raw/sds.html), keyed by `channelId`. This state MAY be persisted within the SDS implementation layer and includes:
- A committed message log recording sent messages and their acknowledgement status.
- An outgoing buffer of unacknowledged message chunks pending confirmation.
- An incoming buffer for partially received segmented messages awaiting full reassembly.
The state MUST be persisted using the `persistence` backend specified in `SdsConfig`.
### Outgoing message processing ### Outgoing message processing
When `send` is called, the implementation MUST process `message` in the following order: When `send` is called, the implementation MUST process `message` in the following order: