Store-and-forward
Last updated
Store-and-forward is a messaging technique in which a device holds a message until a path to the next hop or the destination becomes available, then forwards it. Instead of failing when the recipient is unreachable right now, the message waits on an intermediate device and moves closer whenever connectivity appears. It lets data cross a network that is never fully connected at any single moment.
How it works
Real-time delivery assumes an end-to-end path exists at the instant you send. In intermittent networks that assumption often fails: the recipient is asleep, out of range, or behind a link that is temporarily down. Store-and-forward relaxes the requirement. A device accepts a message, stores it durably, and forwards it when a suitable next hop appears.
This can chain across multiple carriers. A message may sit on one device until it meets a second device heading toward the destination, hand off, and continue. Each holder keeps the message until delivery is acknowledged, and duplicates are suppressed by message ID so a message carried along two paths is delivered once.
The approach underpins delay-tolerant networking, where connectivity is expected to be occasional rather than continuous, and it pairs naturally with multi-hop mesh relaying.
Why it matters
Store-and-forward makes delivery robust when the network is partitioned. A recipient does not need to be online at send time; the message finds its way as connectivity comes and goes.
That is essential for field operations, disaster response, and any setting where devices move in and out of contact, because it turns a series of brief encounters into reliable end-to-end delivery.
How it relates to Offline Protocol
Offline Protocol’s transport layer, DORS, uses store-and-forward together with multi-hop relaying so that a message moves toward its recipient across a mesh that is never fully connected at once. Messages are queued, carry a unique ID and TTL, and are acknowledged on delivery, with senders retrying on timeout and relays dropping duplicates by ID.
The same mechanism carries large payloads: chunked transfer moves files up to 100MB across the mesh with per-chunk acknowledgment and resume. See peer-to-peer mesh networking for how delivery is confirmed end to end.
Frequently asked questions
What problem does store-and-forward solve?
It solves delivery in networks that are not fully connected at any single moment. Instead of failing when the recipient is unreachable, a device holds the message and forwards it when a path appears.
Is store-and-forward the same as a message queue?
They are related. A message queue buffers messages between a sender and a service; store-and-forward extends that idea across a network, where intermediate devices hold and carry the message toward a recipient that may be offline.
Does the message get delivered twice with store-and-forward?
No. Each message carries a unique ID, so a message that travels more than one path is deduplicated and delivered once. Offline Protocol acknowledges delivery and drops duplicates by ID.
