Discover and read the best of Twitter Threads about #WebSockets
Most recents (3)
Wowwwwww today is a day to celebrate! My blog is finally live and the first post is CRAZY nice 😱🔥
👉🏻 bit.ly/blog-ew-websoc…
🧵/1
#javascript #nodejs #learning #blogpost #tutorial #websockets #socketio #diy #100daysofcode
👉🏻 bit.ly/blog-ew-websoc…
🧵/1
#javascript #nodejs #learning #blogpost #tutorial #websockets #socketio #diy #100daysofcode
I've been creating videos on my youtube channel that you rarely will see in another place on the internet 🤩
You'll find there subjects like Recreating @nodejs from scratch, Web APIs and recreating web protocols such as the Web Socket using JS with no frameworks, etc
/2
You'll find there subjects like Recreating @nodejs from scratch, Web APIs and recreating web protocols such as the Web Socket using JS with no frameworks, etc
/2
And others, which are amazing experiments, such as recreating a code coverage tool from scratch and how to process terabytes of data using JavaScript
If you search about those subjects you'd reach out to my videos but why not have them as blog posts as well?
/3
If you search about those subjects you'd reach out to my videos but why not have them as blog posts as well?
/3
Super happy to ship Azure Web Pub Sub! A new azure service for doing pure websockets + HTTP triggering!
azure.microsoft.com/en-us/blog/eas… #azure #websockets
azure.microsoft.com/en-us/blog/eas… #azure #websockets
How is it different from SignalR you ask? Well internally it's built on the same underlying tech but the big difference is that there's no client requirement or protocol requirement, BYOWL (bring your own websocket library).
The mainline scenarios are also focused on severless so we can handle your long running websocket connections and trigger HTTP calls to any backend. It can be azure functions or any addressable HTTP endpoint!
Server-Sent Events or WebSockets?
Why would you need any of them?
Which one should you choose?
Why would you need any of them?
Which one should you choose?
Sometimes you might want to get the latest data from the server without having to poll the server for updates.
This data comes in the form of notifications.
One way of doing this is polling the server for changes periodically but this is not performance friendly
This data comes in the form of notifications.
One way of doing this is polling the server for changes periodically but this is not performance friendly
This is where #WebSockets and Server-Sent Events come in. So what is the difference? in simple terms, in Web sockets, both the client and the server are listening for changes while only the client is listening for changes in Server-Sent Events.
