Re:Removing HTTP/2 Server Push from Chrome
by toast0 on Saturday August 20, 2022 @05:54PM
(#32535470)
Seems like all the churn could have been avoided by webservers advertising a limit on number of connections and browsers opening up to that limit if needed. Maybe in the connection header, or the keep-alive header, or some new header that Google servers and Chrome Browser could have tried out first.
[ Parent
| on HN ]