- From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
- Date: Fri, 13 Jul 2018 14:24:30 +0000
- To: Martin Thomson <martin.thomson@gmail.com>
- CC: Benjamin Schwartz <bemasc@google.com>, Mirja Kühlewind <mirja.kuehlewind@tik.ee.ethz.ch>, "HTTP Working Group" <ietf-http-wg@w3.org>
Martin Thomson: >If you take the rules from h2 directly, then yes, there is no option to coalesce, >because the client remains ignorant of the DNS records that might point to the >same IP address. However, the ORIGIN frame relieves the client of that >constraint and would allow for coalescing in that case. That's a great observation thanks. The ability to coalesce a HTTP connection, that itself could be used to carry "non-HTTP" traffic (subject to a mechanism that allows that to happen) is a pretty powerful capability. Lucas ----------------------------- http://www.bbc.co.uk This e-mail (and any attachments) is confidential and may contain personal views which are not the views of the BBC unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose the information in any way nor act in reliance on it and notify the sender immediately. Please note that the BBC monitors e-mails sent or received. Further communication will signify your consent to this. -----------------------------
Received on Friday, 13 July 2018 14:24:58 UTC