- From: RUELLAN Herve <Herve.Ruellan@crf.canon.fr>
- Date: Thu, 31 Jan 2013 00:05:39 +0000
- To: Poul-Henning Kamp <phk@phk.freebsd.dk>, Patrick McManus <pmcmanus@mozilla.com>
- CC: Roberto Peon <grmocg@gmail.com>, Ted Hardie <ted.ietf@gmail.com>, "Adrien W. de Croy" <adrien@qbik.com>, Eliezer Croitoru <eliezer@ngtech.co.il>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>, John C Klensin <john-ietf@jck.com>
I would think we should do both in parallel: yes this sort of thing will have an impact on the results of those experiments, but this should be mitigated by fine-tuning the code used in the experiment. On the other side, having some early results from the experiments may help us having a better view of what is the tradeoff we have to make. Hervé. ________________________________________ From: Poul-Henning Kamp [phk@phk.freebsd.dk] Sent: Thursday, January 31, 2013 00:36 To: Patrick McManus Cc: Roberto Peon; Ted Hardie; Adrien W. de Croy; Eliezer Croitoru; ietf-http-wg@w3.org; John C Klensin Subject: Re: Do we kill the "Host:" header in HTTP/2 ? Content-Type: text/plain; charset=ISO-8859-1 -------- In message <CAOdDvNrrDhyayThYJz+94C+U+K18gtvEGWqwZ-8-+wP6kH5QRw@mail.gmail.com>, Patrick McManus writes: >and we can apply a requirement to order things :scheme, :host, :uri in >order to facilitate streaming .. And then we're back to my underlying question: Isn't that the sort of thing we should settle before people spend a lot of time on simulating compression and encoding schemes, as this will clearly have significant impact on the results of those experiments ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Received on Thursday, 31 January 2013 00:06:34 UTC