- From: Mark Nottingham <mnot@mnot.net>
- Date: Thu, 10 Jan 2019 12:37:41 +1100
- To: "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
> On 12 Dec 2018, at 1:00 pm, Mark Nottingham <mnot@mnot.net> wrote: > > I've just opened <https://github.com/httpwg/http-extensions/issues/737>. > > """ > Working on evert/structured-headers, @evert noticed that representing the full range of SH integers is hard, and going beyond it can cause problems. > > Given JS's place in the Web ecosystem and the relative rarity of headers that need integers that big (as well as the availability of floats), should we consider limiting the range of integer to match JS? > """ > > Relevant link: http://2ality.com/2013/10/safe-integers.html > For information / comment, a pull request to resolve this: https://github.com/httpwg/http-extensions/pull/749/files Cheers, -- Mark Nottingham https://www.mnot.net/
Received on Thursday, 10 January 2019 01:38:11 UTC