We have a SPDY proof of concept running that will send two GOAWAY frames on
shutdown:
GOAWAY(max stream id, NO_ERROR)
(send ping and wait for pong or timeout)
GOAWAY(last good stream id, *some code*)
TCP FIN
On Thu, May 8, 2014 at 4:01 PM, Daniel Sommermann <dcsommer@fb.com> wrote:
> I'm not very keen on using ALTSVC to indicate a connection draining state.
> Especially since client implementation of alternative services is rather
> fuzzy (not much normative language in that spec), I'd rather stick to a
> mechanism where the client behavior is well understood and requires minimal
> changes to the spec.
>
> I have a slight preference for GOAWAY over DRAINING. With DRAINING we gain
> added explicitness, but at the cost of verbosity (the state diagram would
> grow at least). The spec already establishes that multiple GOAWAYs can be
> received (NO_ERROR followed by some other error during the graceful
> connection shutdown), so I think the work we need to do here is minimal.
> Either mechanism is fine for me, and I'm happy to resolve this at the
> interim.
>
>