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

Re: [#150] Making certain settings mandatory

From: Eliot Lear <lear@cisco.com>
Date: Sat, 29 Jun 2013 22:47:54 +0200
Message-ID: <51CF47FA.7050508@cisco.com>
To: Jeff Pinner <jpinner@twitter.com>
CC: Roberto Peon <grmocg@gmail.com>, Mike Belshe <mike@belshe.com>, Martin Thomson <martin.thomson@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>

On 6/29/13 9:47 PM, Jeff Pinner wrote:
> So devil's advocate -- why make the mandatory during Upgrade?
> If the client is upgrading to HTTP/2.0 and doesn't send them, why
> can't we just assume that the client has accepted the default values?

Because defaults can NEVER be changed.  Sometimes it's better to not
ever have them.
Received on Saturday, 29 June 2013 20:48:28 UTC

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