3 ms·
That's quite the history lesson, thx for the info. I agree that H2 is defacto better than H1, and easier to implement when compared to H3. However, I'll call o
by chucke 3y ago
That's quite the history lesson, thx for the info.
I agree that H2 is defacto better than H1, and easier to implement when compared to H3. However, I'll call out the 2 biggest time sinks of the RFC: stream prioritisation and server push. Both of which had narrow application, and incomplete/inefficient specification. H3 seems to have ditched both. My question is, how did this ever end up in the final RFC? As both seem like the kind of thing that could have been easily disproved in SPDY deployments, as well as just asking people doing HTTP for a living.