Btw great video! But I had just one doubt, the code you showed demonstrates SSE, and as far as I know, it used to work even with HTTP/1.1 So what's the benefit HTTP/2 is providing and how exactly a developer can enable HTTP/2 (or is it just internally handled by the browsers and the server)?
Hey, so trying to do real-time messaging with HTTP/1.1 is like using a flip phone to stream Netflix - it’s just not made for it! 😂 HTTP/1.1 is all ‘you ask, I answer, we’re done,’ while HTTP/2 is like the cool, multitasking wizard that can handle streams and messages flying back and forth like magic. Long-polling or SSE in HTTP/1.1 is like patching a sinking ship with duct tape. So yeah, if you’re thinking of replacing Socket.io, HTTP/2’s your hero! You just have to create a manual functions like publisher and subscriber. That’s it.
Hey, so trying to do real-time messaging with HTTP/1.1 is like using a flip phone to stream Netflix - it’s just not made for it! 😂 HTTP/1.1 is all ‘you ask, I answer, we’re done,’ while HTTP/2 is like the cool, multitasking wizard that can handle streams and messages flying back and forth like magic. Long-polling or SSE in HTTP/1.1 is like patching a sinking ship with duct tape. So yeah, if you’re thinking of replacing Socket.io, HTTP/2’s your hero! Just you have to create a publisher and subscriber as manual functions
![[DRAGON BALL LEGENDS REVEALS ＆ STUFF] LEGENDS FESTIVAL 2024 Special Edition Part 1](http://i.ytimg.com/vi/mV5bGIswTtQ/mqdefault.jpg)
Great video! thanks for sharing
Btw great video! But I had just one doubt, the code you showed demonstrates SSE, and as far as I know, it used to work even with HTTP/1.1
So what's the benefit HTTP/2 is providing and how exactly a developer can enable HTTP/2 (or is it just internally handled by the browsers and the server)?
Hey, so trying to do real-time messaging with HTTP/1.1 is like using a flip phone to stream Netflix - it’s just not made for it! 😂 HTTP/1.1 is all ‘you ask, I answer, we’re done,’ while HTTP/2 is like the cool, multitasking wizard that can handle streams and messages flying back and forth like magic. Long-polling or SSE in HTTP/1.1 is like patching a sinking ship with duct tape. So yeah, if you’re thinking of replacing Socket.io, HTTP/2’s your hero! You just have to create a manual functions like publisher and subscriber. That’s it.
I've been using text/stream unknowningly lol
Hey, so trying to do real-time messaging with HTTP/1.1 is like using a flip phone to stream Netflix - it’s just not made for it! 😂 HTTP/1.1 is all ‘you ask, I answer, we’re done,’ while HTTP/2 is like the cool, multitasking wizard that can handle streams and messages flying back and forth like magic. Long-polling or SSE in HTTP/1.1 is like patching a sinking ship with duct tape. So yeah, if you’re thinking of replacing Socket.io, HTTP/2’s your hero!
Just you have to create a publisher and subscriber as manual functions
Hello
Hello sir
raid