- From: Willy Tarreau <w@1wt.eu>
- Date: Thu, 18 May 2017 08:13:07 +0200
- To: Wesley Oliver <wesley.olis@gmail.com>
- Cc: Kazuho Oku <kazuhooku@gmail.com>, Mark Nottingham <mnot@mnot.net>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>, Patrick McManus <mcmanus@ducksong.com>
On Thu, May 18, 2017 at 07:22:58AM +0200, Wesley Oliver wrote: > Hi, > > Bit late to the part once again. > > Did any one consider, an external reference to preload resource manifest, > which just contains a list of preloaded resources. > The main difference is it is not inline, but external reference resource. > this external reference resource could then be pushed > via http 2.0 to the client, after which it can get to work. Obviously this > would not work with http 1.1 though, > so current solution proposed would be a better than this. I don't see any benefit in doing it like this, it would sound less flexible. In my opinion, providing something to make HTTP/1 to generate server push when relayed via an HTTP/2 edge is really nice. You can imagine a server-side reverse-proxy using this to add some CSS/JS/whatever the application doesn't have to care about, and to provide them to the client when it's done over H2. That's just an example, but I find the current design well balanced between efficiency and flexibility. Regards, Willy
Received on Thursday, 18 May 2017 06:13:47 UTC