- From: Adrian Cole <adrian.f.cole@gmail.com>
- Date: Sun, 28 Sep 2014 15:09:08 -0700
- To: Greg Wilkins <gregw@intalio.com>
- Cc: HTTP Working Group <ietf-http-wg@w3.org>
Agreed. If we are talking trivial changes to implement like switching this back or mucking with static table or huffman codes, I don't mind. They are easy to knock out vs rearranging frames, op-codes, lengths, etc. -A On Sat, Sep 27, 2014 at 7:23 PM, Greg Wilkins <gregw@intalio.com> wrote: > > On 28 September 2014 03:52, Mark Nottingham <mnot@mnot.net> wrote: >> >> I think the time for that has truly past; most of our implementers want to >> get this out the door and running, not do another round of R&D. > > > Just for the record, as an implementer I want neither to just get it out the > door, nor to do another round of R&D. > > I do not believe that the flaws in the protocol can be resolved by simply > iterating the process that we are in. If there was interest in reviewing > the charter, collecting more public data to work against and taking a step > back to truly reviewing what has been produced.... then I'd be all for that > regardless of the time it would take or the pie on our faces. > > Failing that, I'm inclined to not change too much in the current draft - but > if good data is presented to indicate the value of minor changes (eg > switching dynamic/static table, adding values to static table entries, > huffman recoding etc etc.) then I'm happy to follow the data.... at least > for one more round. > > regards > > -- > Greg Wilkins <gregw@intalio.com> > http://eclipse.org/jetty HTTP, SPDY, Websocket server and client that scales > http://www.webtide.com advice and support for jetty and cometd.
Received on Sunday, 28 September 2014 22:09:35 UTC