Description
This is a feature request
Problem
Feature that is useful for application developers is to know if message was actually seen and/or stored by the network.
Proposed Solutions
We need to implement one mechanism for message verification that would consume sender on one end and receiver on another and recognize messages that are not seen by the network or stored there.
This mechanism should populate a pool of messages to be re-send and automatically re-broadcast them with behavior specified in the reliability RFC.
Note: peer renewal
should kick in in case failures happen during sending again and again.
This should be optional feature and enabled by option parameter passed to createLightNode
.
TODO:
- implement message monitoring component that would mark and cache messages that are not sent;
- adapt it to monitor
Filter
and / orStore
; - adapt it to monitor
LightPush
;
- adapt it to monitor
- re-send messages if they are not successfully sent;
flowchart LR
LightPush --> MessageMonitor
Filter --> MessageMonitor
MessageMonitor-- resend marked messages -->LightPush
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
To Do