Short transfer

How it works

Handshake, TLS, and directory checks can exceed the byte time. Batching short files into one object changes the class. Integrity checks still apply and are cheap.

Fifty 80 KB files over SFTP take 40 seconds. One tar of the same files takes 3 seconds. The difference is setup, not bandwidth.

How it differs

Short is about duration, not importance.

A timeout set for large files never fires here. Failures are auth and path, not stalls.

Log the setup error.

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 short 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 short 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.