Technical Reference

SFRM

Large files cut into segments, each checked with a checksum, optionally signed and encrypted, and acknowledged when the whole file has arrived.

SFRM is built for the case ebMS and AS2 weren't: very large files. Rather than sending one message, Archr.Hermod cuts the file into segments (1 MB each unless the server is set otherwise), works out an MD5 checksum for each, and posts them one at a time over HTTP or HTTPS. The receiver checks every segment against its checksum and puts the file back together. If a segment fails to arrive, only that segment is sent again โ€” not the whole transfer.

When the partnership asks for it, each segment is signed and encrypted on its own (CMS/PKCS#7). A segment that is meant to be signed is never sent unsigned: if it cannot be signed, it is not sent, the transfer fails, and the reason is logged. The file's name and total size travel with every segment, and when the receiver has the whole file it sends an acknowledgement back.

How Archr.Hermod configures it

The number of retries and the time between them are set per partnership; the segment size is a setting of the server. A transfer is shown as waiting, being sent, sent and waiting for the acknowledgement, acknowledged, or failed, and a failed one keeps its reason, so a stalled large-file transfer is something you can see and act on, not something that silently times out.

Step by step, from the partnership to following a transfer: the SFRM guide.

โ† Back to the technical reference