Re: Design Issue: Max Concurrent Streams Limit and Unidirectional Streams from James M Snell on 2013-05-02 (ietf-http-wg@w3.org from April to June 2013)

From: James M Snell <jasnell@gmail.com>
Date: Thu, 2 May 2013 10:41:01 -0700
To: Martin Thomson <martin.thomson@gmail.com>
Cc: William Chan (陈智昌) <willchan@chromium.org>, Roberto Peon <grmocg@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
Message-ID: <CABP7RbfbmTqFHPkRvj2K6iZ=Oo7MsT3hD9Y33fmtU9HOLoDmUA@mail.gmail.com>

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 Thursday, 2 May 2013 17:41:49 UTC