kopia lustrzana https://github.com/meshtastic/firmware
Update StoreForwardPlugin.md
rodzic
a4fd74b58e
commit
b35cd76854
|
@ -51,6 +51,10 @@ In this case, we have two routers separate by a great distance, each serving mul
|
|||
|
||||
Q: How do we rejoin both fragmented networks? Do we care about messages that were unrouted between fagments?
|
||||
|
||||
## Identifing Delayed Messages
|
||||
|
||||
When a message is replayed for a node, identify the packet as "Delayed". This will indicate that the message was not received in real time.
|
||||
|
||||
# Router Data Structures
|
||||
|
||||
Structure of received messages:
|
||||
|
@ -90,4 +94,4 @@ On every handled packet, if we have not heard from that sender in a period of ti
|
|||
|
||||
# Designed limitations
|
||||
|
||||
The Store and Forward plugin will subscribe to specific packet types and channels and only save those. This will both reduce the amount of data we will need to store and reduce the overhead on the network. Eg: There's no need to replay ACK packets nor is there's no need to replay old location packets.
|
||||
The Store and Forward plugin will subscribe to specific packet types and channels and only save those. This will both reduce the amount of data we will need to store and reduce the overhead on the network. Eg: There's no need to replay ACK packets nor is there's no need to replay old location packets.
|
||||
|
|
Ładowanie…
Reference in New Issue