A Guide to HTTP/2 Server Push

Re:A Guide to HTTP/2 Server Push by jimktrains2 on Monday April 10, 2017 @01:05PM (#14080357)

Or, what may be a more common case, depending on caching method:

Without server push:

1. Client requests main page ->

2. Client receives main page <-

With server push:

1. Client requests main page ->

2. Client receives push promises and main page <-

3. Client cancels promises it doesn't need ->

[ Parent | on HN ]

Re:A Guide to HTTP/2 Server Push by Ajedi32 on Monday April 10, 2017 @05:20PM (#14082663)

Ah, fair point. Now I see what you were trying to say.

Assuming the server has no way of determining which assets the client has cached (which depending on implementation may not be the case) you're of course correct. However, after step 2 the page has already fully loaded in both cases, so step 3 doesn't really slow anything down.

[ Parent | on HN ]