2GB file transfer

How it works

Two gigabytes is 16,000 megabits. At 10 Mbps that is about 27 minutes. Browser tabs suspend. A resumable offset beats a second full POST.

A 2.0 GB cut starts at 21:10. The lid closes at minute 14. Resume continues from 1.3 GB and makes a 22:00 review. A plain form misses it.

How it differs

Two gigabytes is the same door as 1 GB with a worse timeout budget.

A 15-minute expiry is shorter than a 5 Mbps download of this size, which wants about 53 minutes.

Do not mark sent when the upload finishes. The download is a second clock.

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 two gb 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 two gb 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.