3 ms·

The real question is, why is this not part of the base internet protocols already? Only goes to show how TCP is not as reliable as it should

kccqzy 4y ago
There are many older and more venerable file transfer protocols, like FTP or TFTP. Add encryption and then you have SCP and SFTP. SFTP is the default protocol used by the scp command, and TFTP is still often used to communicate with routers and access points and similar equipment. And I'm not sure what that has anything to do with TCP not as reliable. TCP has real problems on the modern Internet but the first part does not imply the second part.
- raverbashing 4y ago
  And none of those protocols keeps the connection alive if you unplug your network cable and plug it back on really quickly Might I say, even if you get the same IP back from the router
  - kccqzy 4y ago
    That's not a problem with TCP, that's more of a problem with IP itself. Connections are currently identified by the source/destination IP and port numbers, but that should not have been the case. Imagine we use a UUID for the connection and keep an updatable cache between UUID and IP. Still nothing to do with TCP. Also, this kind of partial file transfer protocol is still needed because what if a host crashes? Even if we completely solve the mobile IP problem we would still rely on both ends of the connection tracking state. That state is lost due to a crash or power failure.
manigandham 4y ago
What does this have to do with TCP being reliable?
- raverbashing 4y ago
  If TCP was reliable enough, then these chuncked transfers wouldn't need to be used
  - manigandham 4y ago
    These chunked transfers are used to efficiently sync only the changed parts of the file. The actual network traffic is still over TCP. You're conflating several layers and abstractions.

3 ms·

The real question is, why is this not part of the base internet protocols already? Only goes to show how TCP is not as reliable as it should

by raverbashing 4y ago

kccqzy 4y ago
There are many older and more venerable file transfer protocols, like FTP or TFTP. Add encryption and then you have SCP and SFTP. SFTP is the default protocol used by the scp command, and TFTP is still often used to communicate with routers and access points and similar equipment. And I'm not sure what that has anything to do with TCP not as reliable. TCP has real problems on the modern Internet but the first part does not imply the second part.
- raverbashing 4y ago
  And none of those protocols keeps the connection alive if you unplug your network cable and plug it back on really quickly Might I say, even if you get the same IP back from the router
  - kccqzy 4y ago
    That's not a problem with TCP, that's more of a problem with IP itself. Connections are currently identified by the source/destination IP and port numbers, but that should not have been the case. Imagine we use a UUID for the connection and keep an updatable cache between UUID and IP. Still nothing to do with TCP. Also, this kind of partial file transfer protocol is still needed because what if a host crashes? Even if we completely solve the mobile IP problem we would still rely on both ends of the connection tracking state. That state is lost due to a crash or power failure.
manigandham 4y ago
What does this have to do with TCP being reliable?
- raverbashing 4y ago
  If TCP was reliable enough, then these chuncked transfers wouldn't need to be used
  - manigandham 4y ago
    These chunked transfers are used to efficiently sync only the changed parts of the file. The actual network traffic is still over TCP. You're conflating several layers and abstractions.