Wanna feel old?
-
And this:
Future HTTP protocols will be back-compatible with this protocol.
Assurance of future compatibility right from the start, leaving all future implementations with a known starting point to discover/negotiate new capabilities.
These slides (PDF) give a pretty good technical outline/summary of how HTTP has evolved from 1991 to late 2022.
-
And this:
Future HTTP protocols will be back-compatible with this protocol.
Assurance of future compatibility right from the start, leaving all future implementations with a known starting point to discover/negotiate new capabilities.
These slides (PDF) give a pretty good technical outline/summary of how HTTP has evolved from 1991 to late 2022.
@Axtremus said in Wanna feel old?:
These slides (PDF) give a pretty good technical outline/summary of how HTTP has evolved from 1991 to late 2022.
Hey, nice slides!
Do you have any thoughts on bringing quality of service methods into the WWW protocol stack? E.g., bandwidth or latency guarantees.
-
@Axtremus said in Wanna feel old?:
These slides (PDF) give a pretty good technical outline/summary of how HTTP has evolved from 1991 to late 2022.
Hey, nice slides!
Do you have any thoughts on bringing quality of service methods into the WWW protocol stack? E.g., bandwidth or latency guarantees.
@Klaus said in Wanna feel old?:
@Axtremus said in Wanna feel old?:
These slides (PDF) give a pretty good technical outline/summary of how HTTP has evolved from 1991 to late 2022.
Hey, nice slides!
Do you have any thoughts on bringing quality of service methods into the WWW protocol stack? E.g., bandwidth or latency guarantees.
Klaus, the thread is 'Wanna feel old' not freaking suicidal