Folder transfer

How it works

Each member is its own transfer unless you pack the tree. SFTP and WebDAV can MKD and PUT per file. A browser usually cannot send a folder without a packager or a directory-upload API. Empty directories and dotfiles are the members people forget. Completion is every file present at the expected size, not the parent name existing.

A job sends 800 files in three nested folders over SFTP. File 640 fails. The parent folder exists. A check that only lists the top level says success. A manifest of relative paths and sizes shows 640 missing. The rerun sends the missing member only.

How it differs

Folder transfer is not ZIP transfer. You can retry one member. You also pay a round trip per member. Pack when the tree is chatty. Send members when the recipient must fetch one file.

Case-sensitive servers store Cut.mov and cut.mov as two files. A Windows download folder collides them. Normalize names before the send.

Symlinks may be sent as links or as copies. Agree which, or the recipient gets a pointer to a path that does not exist.

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.