XPost: alt.comp.os.windows-11   
   From: daniel47@somewhere.someplaceelse   
      
   On 9/09/2025 9:14 pm, Carlos E.R. wrote:   
   > On 2025-09-09 12:54, Daniel70 wrote:   
   >> On 9/09/2025 1:20 am, R.Wieser wrote:   
   >>> Daniel,   
   >>>   
   >>>>>> But how does the distant end know when I have received the   
   >>>>>> entire file (i.e. Download end time)??   
   >>>   
   >>> As said, the sending-side marks the last to-be-send data-block as   
   >>> being ... well, the last block.  :-)   
   >>>   
   >>>>>> Similarly, how does the distant end know when my computer   
   >>>>>> started the Upload (Upload start time)??   
   >>>   
   >>> By receiving the first block of data ?   
   >>>   
   >>> Mind you, files do *not* get send as a single block, but as a   
   >>> number of smaller blocks.   
   >>>   
   >>> Regards, Rudy Wieser   
   >>>   
   >> Yes, understood, Rudy, don't start sending second Block until   
   >> reception of first block acknowledged.   
   >   
   > Hum. Maybe not. I did not study TCP in that detail, but older   
   > protocols would send a number of blocks, say 1, 2, 3, 4 & 5 and start   
   > receiving the ACKs after number 3. The receiver says OK to number 1,   
   > fail number 2, Ok number 3... so after a while, out of sequence, the   
   > sender repeats number 2, just after sending number 6.   
   >   
   During my Military Service, I worked at The Australian Army's Primary   
   H.F. Transmitter site. Most of our signals were multi-channel TTY over   
   an A.F. channel. Just kept sending. If there was a corruption, that'd   
   get resent later, if needed.   
      
   One circuit operated as you described above, virtually Byte-by-byte   
   error detection and correction.   
   --   
   Daniel70   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)