Re:CSS and JS code coverage in Chrome DevTools
by i_live_ther3 on Wednesday July 12, 2017 @08:40AM
(#14751962)
What happened with shipping everything in a single file and letting cache magic happen?
[ Parent
| on HN ]
Re:CSS and JS code coverage in Chrome DevTools
by davideast on Wednesday July 12, 2017 @09:04AM
(#14752130)
HTTP/2 happened. HTTP/2 allows you to send HTTP requests over a single TCP connection per domain. Headers are compressed. The request overhead is minimal compared to HTTP/1.x.
Caching one big file has the draw back of busting the cache each time the file is updated for any small change.
Caching multiple small files allows you to have a finer grain cache. Only bust the things that updated. And, since it's all the same TCP connection it's now performant to load this way.
Re:CSS and JS code coverage in Chrome DevTools
by koolba on Wednesday July 12, 2017 @09:13AM
(#14752190)
Can't you do that already by reusing the 1.1 connection? Or is the 2.0 change that requests are now parallel?
Re:CSS and JS code coverage in Chrome DevTools
by davideast on Wednesday July 12, 2017 @09:55AM
(#14752517)
Yep, more wording was bad. In HTTP/2 it's all parallel.
Re:CSS and JS code coverage in Chrome DevTools
by swiley on Wednesday July 12, 2017 @09:26AM
(#14752297)
>HTTP/2 allows you to send HTTP requests over a single TCP connection per domain.
HTTP/1.x definitely has support for this. Not using it actually may get your IP temporarily blocked from many sites.
Re:CSS and JS code coverage in Chrome DevTools
by davideast on Wednesday July 12, 2017 @09:54AM
(#14752511)
Sorry, wrote this before coffee. I was referring to H/2 eliminating head-of-line blocking. HTTP/2 gives you one TCP connection for multiple requests rather than the 7 connection limit browsers impose on HTTP 1.x