W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2014

Re: END_SEGMENT and END_STREAM redundant

From: David Krauss <potswa@gmail.com>
Date: Sun, 20 Apr 2014 08:58:42 +0800
Cc: Adrian Cole <adrian.f.cole@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <95991A2E-5535-4C46-B3BA-142CAD996427@gmail.com>
To: Roberto Peon <grmocg@gmail.com>
This is similar to my earlier question about duplicate segment codings. The spec needs to specify which is significant (observable by the application): the flag bits, or the segmentation.

On 20140420, at 6:23 AM, Roberto Peon <grmocg@gmail.com> wrote:

> Arguably these are not redundant, since the message may not have been completed when the stream was terminated.
> -=R
> 
> On Apr 19, 2014 8:08 AM, "Adrian Cole" <adrian.f.cole@gmail.com> wrote:
> Hi, all.
> 
> The combination of END_SEGMENT and END_STREAM seem redundant to me.
> It seems like you wouldn't need to support both flags at the same
> time, as ending a stream surely ends the segment.  Is it worthwhile
> calling this out?
> 
> -A
> 


Received on Sunday, 20 April 2014 00:59:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:30 UTC