Re:Nginx Patch: SPDY/3.1 protocol implementation
by stingraycharles on Tuesday January 28, 2014 @04:20AM
(#7136180)
A version number is just an arbitrary point in time, in the case of SPDY, with a certain feature set. Just because SPDY/2 doesn't support everything SPDY/3 supports doesn't mean it's unstable.
This is why I like date-based version numbering, such as Ubuntu 13.10 or C++11.
Re:Nginx Patch: SPDY/3.1 protocol implementation
by StavrosK on Tuesday January 28, 2014 @06:09AM
(#7136431)
But date-based numbering provides no information other than the date the code was released on. Semver, on the other hand, conveys much more.
Re:Nginx Patch: SPDY/3.1 protocol implementation
by youngtaff on Tuesday January 28, 2014 @04:23AM
(#7136189)
SPDY version numbers will increasing clock up, HTTP/2.0 numbers are likely to be far more less frequent
Re:Nginx Patch: SPDY/3.1 protocol implementation
by lucian1900 on Tuesday January 28, 2014 @05:07AM
(#7136294)
It's still a draft.
All those changes to, say, 802.11n, WebSockets or OAuth2? Drafts too.
So HTTP 1.1 lasted for 20 years without significant changes, but SPDY which has been around for a year or so and is already on version 3, with extra point-releases for shit and giggles.
If you're going to create a protocol and want it to be used internet-wide can you at least plan up front and keep things stable once released?
Glad I don't have to maintain and deploy any code related to this. Jesus christ.