Ok, you monkeys
Get your damned nomenclature right.
When I’m standing at a terminal and transferring a file from an external node to my terminal, that is a download. When I’m transferring a file from the terminal to the external node, that is an upload. When I’m transferring a file from one node to another, that is a transfer. Got it?
Instead, when I transfer a file from machine A to machine B, you call that an upload. But when I transfer a file from machine A to machine C, you call that a download. When I transfer a file from machine C to machine A it’s an upload again, but from machine C to machine B it’s a download. And when I transfer a file from machine A or machine B to the terminal, its an upload, but from machine C to the terminal, it’s a download. And of course the converse is true.
What?
Anyway, I get that this was a simpler- er, more complex time, and you had to fight with strange protocol like RS423, and serial networks are never simple, but at least stick to one pattern, futhuchrissakes. I have to have a cheat sheet to get anything done.
Oh, and thanks for PARTIALLY disabling the floppy drives so they spin but don’t read. Took half a day to figure THAT one out.
Do you know how many times I’ve been told to download a file from the PC to the mainframe? Sigh.
Oh, and don’t get my started with trying to explain to my managers what a “server” is. “Server” (aka waitress) is what my project leader would have been had she not been young and cute when she applied for the job with two males interviewing her (one of whom is now both her manager and her boyfriend). Definitely could have had a rewarding career in either the food service or housekeeping industries, or perhaps in one of the dumpier strip joints in central NJ.
Personally I consider all of them file transfers, or file copies. The mundanes have completely corrupted the terms “download” and “upload”.
Download is to the referent, upload is away from the referent.