3 ms·
Probably each TCP connection only goes over one IP address, so the remote end doesn't get confused. All the data coming back on that connection will have to com
by wmf 13y ago
Probably each TCP connection only goes over one IP address, so the remote end doesn't get confused. All the data coming back on that connection will have to come in on the same path the connection started on.
- chacham15 13y agoIf that were the case, the download would be no faster than using a single connection. I guess it would help if you download multiple things, but that is a different claim than what is claimed in the title.
- mikeash 13y agoYou can use multiple connections for a single download (e.g. HTTP range requests).
- anoncow16 13y agoI was thinking the same thing. A quick glance at the code (I don't speak js) seems it's not doing this.
- chacham15 13y agoYes, but that is at the application layer, not the transport layer (i.e. at TCP). Meaning, you need to be aware of what is actually being sent.
- mikeash 13y agoWell, if you just balance TCP connections across physical connections, you could then combine this with a multi-connection HTTP download client and get the effect without any one piece having knowledge of it all (aside from the human). But yes, it's not going to be useful in general for everything.