One of the most amazing video that I have came across on websockets. Rather than directly jumping on to the code - its very important to figure out the reason why web sockets exists- thanks for explaining that.
Thanks for this video. It explains alot. Question: Should we socket be used for video streaming? Does using websocket increase data cost? What about speed?
its really nice videos i had across till now very simple Explanation with comparison with the HTTP protocol. I can say very useful for to understand the web socket and why to go for and why to not Thanks for posting such interesting videos please keep it ahead so we can gain our existing technical skills.
@tech primers - for the chat application, you are saying everytime we refresh the browser the data will be lost since the connection is lost. It doesn't happen like that in Whatsapp right? What is different in whatsapp then?
Good fundamental concepts. I have a unique requirement. API sends huge amount of data to UI and sometimes it throws "Broken pipe error" from backend, sometimes UI can't get whole response though response is 200 OK . Can I use it here ?
1 - before web socket how chat system works real time like (fb) 2 - how counter strike 1.6 old one works ( its chat system ) 3 - web sockets sending empty payload to servere in case of idel ? 4 - when client connect to server , where servere strore this client is connected ?
How resource intensive is keeping a websocket open over just using REST calls every 20 seconds or so? That's the one thing I have not been able to wrap my head around with sockets is how much RAM do I need for a live app that could have X amount of concurrent connections at any given time.
can you plz make a vid tut on how to make a web socket node js via php secure with cert and key files ? and have you got github link to the code you used?
When you refresh a page, does the browser notify the server to forget about the old websocket connection. How does server know that not that connection is invalid now.
Most likely a new session ID is given to the client from the server everytime a new client requests to connect to the server. So if you refresh a page, you client sees you as another "new" connection.