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

Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams

From: (wrong string) 陈智昌 <willchan@chromium.org>
Date: Fri, 3 May 2013 13:44:46 -0300
Message-ID: <CAA4WUYj81k1dK-LV+=h-yto4WEpVWFaRnCQZ+h55mipYCnQeYw@mail.gmail.com>
To: James M Snell <jasnell@gmail.com>
Cc: Martin Thomson <martin.thomson@gmail.com>, Roberto Peon <grmocg@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
I'd like server folks to chime in, but doing this makes me feel a bit
nervous. I feel this effectively disables the directional concurrent
streams limit. The bidirectional full-close essentially acts like an ACK,
so removing it might result in an unbounded number of streams.


On Thu, May 2, 2013 at 2:41 PM, James M Snell <jasnell@gmail.com> wrote:

> That works too. If folks are agreement on that particular approach I
> can work up the spec changes necessary to describe stream state in
> those terms.
>
> On Thu, May 2, 2013 at 10:22 AM, Martin Thomson
> <martin.thomson@gmail.com> wrote:
> > I think that this is going in the wrong direction.
> >
> > If you consider that streams are not the owners of state, but each
> > direction is the owner of state, then this whole issue disappears.
> > For a push, the client->server direction never opens*.  Simple.  No
> > flags.
> >
> >[snip[
>
Received on Friday, 3 May 2013 16:45:17 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 1 March 2016 11:11:12 UTC