-
-
Notifications
You must be signed in to change notification settings - Fork 106
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Chrome intends to remove support of Server Push technology #70
Comments
I published a Twitter thread explaining what it changes for Vulcain: https://twitter.com/dunglas/status/1326552735404060672 TL;DR Vulcain will fallback on |
Got it, thanks |
How will the updated approach be faster than a compound document if there is a minimum of 2 RTT to implement the protocol? |
@sbward because HTTP cache. The cache dynamic is better with many small documents instead of a big compound one. And actually the cache dynamic will be better with 103 than with server push because browsers never properly supported HTTP cache for pushed resources(even if theoretically possible). |
Conversation
The text was updated successfully, but these errors were encountered: