21–30 of 89 posts
Earlier quoted context omitted.
No, it stands for "General Termination of Future Operations."
no, its both :P
This play on words is a pretty okay joke.
Earlier quoted context omitted.
The old Unix model (simple, do one thing, text formats, etc.) is dead. The world has come to prefer code and protocols which perform well at scale.
Since the semantics of 1.1 and 2.0 are the same (besides push) you can choose which encoding you prefer based on your requirements and constraints. In fact, maybe we should rename HTTP/1.1 to "HTTP/2.0 Textual Encoding" or something so that people can feel like they're not missing out on anything. It worked for USB 2.0.
Let's not taint good, old HTTP in the process please.
Earlier quoted context omitted.
no, its both :P
It also stands for Great Tanzanian Flying Orangutans and thousands of other things (in the sense that it forms an initialism of those words), but the standard definitely uses General Termination of Future Operations.
Also noticed further down, the error code ENHANCE_YOUR_CALM
I still can't decide whatever it's childish or fking awesome!
The complexity difference between HTTP1 and HTTP2 is pretty huge. Not sure if they're even remotely the same protocol anymore.
Agreed. This spec reads more like a brand new and complex transport protocol than an application one. Is it HTTP 2.0's plan to completely replace "middleware" like SPDY with a full featured protocol?