simplify dispatch step

This commit is contained in:
Ivan FB 2026-04-29 18:27:05 +02:00
parent 0b3a4aeb5c
commit 8483bb10d9
No known key found for this signature in database
GPG Key ID: DF0C67A04C543270

View File

@ -157,10 +157,7 @@ When `send` is called, the implementation MUST process `message` in the followin
2. **Apply [SDS](https://lip.logos.co/ift-ts/raw/sds.html)**: register each segment in the SDS outgoing buffer (see [SDS](#scalable-data-sync-sds) for parameter bindings).
3. **Encrypt**: If an `Encryption` implementation is provided, encrypt each segment before transmission.
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 segment via the underlying [MESSAGING-API](/standards/application/messaging-api.md).
- Update the persisted MessageId entry, in point 2., with the sent MessageHash, only when
the event `MessageSendPropagatedEvent` is triggered (that event is defined in [MESSAGING-API](/standards/application/messaging-api.md)).
5. **Dispatch**: Send each segment via the underlying [MESSAGING-API](/standards/application/messaging-api.md).
### Incoming message processing