TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

How HTTP/2 Pushes the Web

58 点作者 lainon超过 6 年前

4 条评论

Animats超过 6 年前
If you need push to get a web page displayed fast, the page is probably loading too much crap.
tracker1超过 6 年前
I think one of the bigger issues is tooling around creating web applications and related content. For now, webpack and other bundlers do a pretty decent job of grouping bundles together, however the additional costs for handling routing or server-rendering&#x2F;caching in order to determine which bundles to push is a bit in the dark.<p>I think we will definitely get there in the near future. I also think that one can definitely get a well-crafted application together by hand, but until the tooling catches up, it will not be widely used.<p>One thing that could be done is a webserver that tracks which resources are most commonly requested within say 5 seconds of an initial resource, and if &gt;N% of them also request a given resource, it gets pushed by default. That could be a good starting point, but then comes the cost of keeping those relations&#x2F;counts&#x2F;tables in memory and not overloaded.<p>Definitely some opportunities out there.
hkai超过 6 年前
What&#x27;s the state of discussion of the disadvantages of HTTP&#x2F;2 now?<p>A few years ago I heard the argument that it basically benefits Google and other large companies and inconveniences everyone else.
评论 #18217409 未加载
评论 #18217663 未加载
denormalfloat超过 6 年前
PUSH PROMISE is great and all, but the use is limited. If the remote side already has the asset you push (because it&#x27;s cached), you waste your bandwidth and increase latency.
评论 #18217628 未加载