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

Re: GOAWAY and proxies (#458)

From: Roberto Peon <grmocg@gmail.com>
Date: Fri, 2 May 2014 20:44:29 -0700
Message-ID: <CAP+FsNdHBrvirT3_m0RaS75koZgXyS=G80WEa6j1SNPHEw=dQA@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: William Chan (陈智昌) <willchan@chromium.org>, Daniel Sommermann <dcsommer@fb.com>, HTTP Working Group <ietf-http-wg@w3.org>
DRAINING is a signal that indicates that the server will be sending a
GOAWAY in the near future, and thus that the client should create a new
connection, but, unlike GOAWAY it does not require the client to stop
sending requests.
This allows for a far more seamless switch-over without requiring the
state-tracking of ALT-SVC.


On Fri, May 2, 2014 at 8:36 PM, Martin Thomson <martin.thomson@gmail.com>wrote:

> On 2 May 2014 15:30, William Chan (陈智昌) <willchan@chromium.org> wrote:
> > The way our code works right now is, on receipt of a GOAWAY, we put
> > ourselves in a lame duck mode and kill all streams above the last
> accepted
> > stream id with an error code to retry them. If we're already in the lame
> > duck mode, great. We don't track anything about previous accepted stream
> > ids.
> Perfect.  No extra logic.  If you get an extra GOAWAY, you might kill
> a few more requests.
> What does the extra explicitness of DRAINING actually buy?
Received on Saturday, 3 May 2014 03:44:55 UTC

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