This process results in faster load times.
Ask HN: Would you pay to reduce HTTP requests?
1–9 of 9 posts
Re: Ask HN: Would you pay to reduce HTTP requests?
#2Re: Ask HN: Would you pay to reduce HTTP requests?
#3Re: Ask HN: Would you pay to reduce HTTP requests?
#4As a viewer? As a publisher?
Re: Ask HN: Would you pay to reduce HTTP requests?
#5How would you outcompete major CDNs/existing caching schemes already being paid for?
If you load 10 images in 1 request, you've reduced network latency and avoided the connection limit.
Re: Ask HN: Would you pay to reduce HTTP requests?
#6Re: Ask HN: Would you pay to reduce HTTP requests?
#7How would you outcompete major CDNs/existing caching schemes already being paid for?
They don't reduce request count. For example, Chrome only allows 6 concurrent connections (requests). If you load 10 images in 1 request, you've reduced network latency and avoided the connection limit.
Re: Ask HN: Would you pay to reduce HTTP requests?
#8Earlier quoted context omitted.
They don't reduce request count. For example, Chrome only allows 6 concurrent connections (requests). If you load 10 images in 1 request, you've reduced network latency and avoided the connection limit.
Does that limit still apply with HTTP 2 and HTTP 3?
Re: Ask HN: Would you pay to reduce HTTP requests?
#9The question is very vague, and kind of fails the "Mom test".
The concept of a "mom test" is condescending as well. Many moms code.