72 ms·
It's good, but it's still many requests over network latency and could be improved if it was one connection, one download, for the whole page.
by jodrellblank 17y ago
It's good, but it's still many requests over network latency and could be improved if it was one connection, one download, for the whole page.
- lsc 17y agohttp://en.wikipedia.org/wiki/HTTP_persistent_connection http://en.wikipedia.org/wiki/HTTP_persistent_connection if everything on the page is from one server, it will all go over one connection. In the case of using a http cache, all the connections are made by the cache, and one connection is made to the cache by the end-user box.
- jodrellblank 17y agoBut that's about using the same TCP connection to make multiple HTTP requests, whereas the proposal is to use one TCP connection and one HTTP request, e.g. COMPOUND-GET /index.html and the server sends a .gz of all required files / data to render index.html. (Not sure that would work so well with very dynamic, crosslinked and javascript heavy sites, but text and images might be possible).