4 ms·
I’ll bite. I like HTTP/2. It may be too complicated for what it was designed to do, i.e serving web resources, but it’s really good at doing things that it wasn
by zarzavat 2y ago
I’ll bite. I like HTTP/2. It may be too complicated for what it was designed to do, i.e serving web resources, but it’s really good at doing things that it wasn’t designed to do.
If you need something more complicated than what a browser does with HTTP, with a lot of bidirectional communication, then HTTP/2 makes for a great alternative to WebSockets. HTTP isn’t just used in browsers but also for server-server, mobile-server, IPC, etc. HTTP/1.1 isn’t always good enough for that.