[sldev] [ARCH] Certified HTTP Project Update - Oct 25

[Argent Stonecutter]

On 29-Oct-2007, at 12:28, Callum Lerwick wrote:
> On Fri, 2007-10-26 at 17:12 -0500, Argent Stonecutter wrote:
>> Send a sequence
>> number with the update and you can tell if you missed one, and
>> periodically send back a "mass ack" with a list of missed sequence
>> numbers since the last mass ack, with some kind of RLL coding for big
>> gaps.

> ... In other words, use TCP. (Specifically, RFC 2018)

SACK doesn't include letting the application layer know about missed  
segments, nor does it allow the application layer to decide whether  
to retransmit a missed segment or not. TCP is a reliable transport,  
every byte put into the pipe must get to the other end, and as far as  
the application is concerned all this stuff happens under the hood.  
We don't care if all of the last 10 texture changes on face 0 got to  
the client or not, so long as the 11th one gets there.