search

dunglas / vulcain

🔨 Fast and idiomatic client-driven REST APIs.
https://vulcain.rocks
GNU Affero General Public License v3.0
3.52k stars 104 forks source link

Chrome intends to remove support of Server Push technology #70

Closed qWici closed 1 year ago

qWici commented 4 years ago

Conversation

dunglas commented 4 years ago

I published a Twitter thread explaining what it changes for Vulcain: https://twitter.com/dunglas/status/1326552735404060672

TL;DR Vulcain will fallback on Preload links (which are already supported) and Early Hints when they will be adopted by browsers. Preload links introduce a bit more latency than Server Push (1 RTT actually), but also fix some issues. Anyway, even with Preload links instead of Server Push, the global approach is still faster and cleaner than using compound documents.

qWici commented 4 years ago

Got it, thanks

sbward commented 2 years ago

How will the updated approach be faster than a compound document if there is a minimum of 2 RTT to implement the protocol?

dunglas commented 2 years ago

@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).

chalasr commented 1 year ago

I suppose this can be closed: #95 #122