4 ms·
Version 3.1? OK. 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
by josteink 13y ago
Version 3.1? OK.
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.
- stingraycharles 13y agoA 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.
- StavrosK 13y agoBut date-based numbering provides no information other than the date the code was released on. Semver, on the other hand, conveys much more.
- youngtaff 13y agoSPDY version numbers will increasing clock up, HTTP/2.0 numbers are likely to be far more less frequent
- lucian1900 13y agoIt's still a draft. All those changes to, say, 802.11n, WebSockets or OAuth2? Drafts too.
- IvyMike 13y agoHow long did HTTP 0.9 last? How about 1.0? I guess you think that early http was one of those non-stable not-suitable-for-internet-wide release protocols.