Transfer queue

How it works

The queue absorbs bursts so 40 people do not open 40 streams at 09:00. Priority lets a payroll file pass a log upload. A queue without a dead-letter hides poison files that retry forever.

Twelve 2 GB deliveries enqueue at 18:00. Two workers run, capped at 50 Mbps each. The last file starts at 19:10. A payroll file marked priority starts next. Without the queue, the office link saturates at 18:00.

How it differs

A queue is not a folder. A folder has no order and no retry state.

A worker crash that does not return the job to the queue loses the file until someone notices.

Ack after success, not after pop.

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 transfer queue, 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 transfer queue 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.