Small file transfer

How it works

Thousands of 20 KB files pay a handshake each. One archive pays it once. Integrity rules do not get smaller with the file.

Four thousand invoices, 30 KB each, one session per file, 180 ms away, spend about 12 minutes on setup. A zip of the same 120 MB uploads in seconds.

How it differs

Small is not unimportant. A 4 KB payment file can be the audited one.

Thousands of parallel sessions look like an attack.

Pipeline or pack.

On the ticket

• The practical close is a log line: time, actor, byte count, result.
• Without that line the transfer is a story.
• With it, the next person can see whether this door did what the ticket claimed.
• If the path is shared, say so in the partner profile so a later change does not silently pick a different limit, key, or region.
• On a real ticket, write down the door, the byte count, and the clock.
• For small file transfer, that means naming the host or bucket, the expected size, and the time the other side must have a complete file.
• A progress bar is not that record.
• A 200 response that arrives before the complete call is not that record.
• If a retry is allowed, say how many and whether it resumes.
• If a person must approve the send, name the person.
• Partners who receive small file transfer files should match on hash or size before they import.
• A same-length corrupt file passes a size check and fails a hash.
• Keep the published hash off the only channel an attacker can edit, or treat it as a corruption check rather than a substitution check.
• When the path changes, new key, new region, new cap, update the profile the same day so the next run does not use a stale limit.