WebSockets an Introduction and Deep Dive

[@RineezAhmed]

Thanks for the deep explanation. That's exactly what I was looking for!

[@pragmaticsoftwareengineer7965]

I am so glad I stumbled upon your channel Shiv. Your content is top-notch and easy to digest even for advanced topics. Thank you for doing what you're doing here. Really appreciate it.

[@Matlus]

Thank you for your kind words. Very inspiring.

[@sumitmore4680]

Shiv, excellent video as always. Super cool demo 🙌🏻. Websocket is one of my fav topics. Thanks for posting video on it.

[@Matlus]

Thank you Sumit! Glad you liked it.

[@dchennaraidu]

A revision of my Computer Networks subject, thank you Shiv 🙏

[@Matlus]

Thank you Chenna! Appreciate the comment.🙏

[@saurabhchauhan232]

Thank you for an awesome explanation, as always the beauty of your channel is what ever you explain is from the basics. Excited for next sunday notification, Really appreciate your efforts.

[@Matlus]

Thank you for your comment Saurabh! Glad you appreciate the need to understand and discuss the foundations for things rather than just the actual topic/technology.

[@ivanvincent7534]

Great content as always. The graphics that are added to support your knowledge share are an excellent addition IMO. Looking forward to the rest of the series on this topic.

[@Matlus]

Much appreciated! Glad you like them too!

[@himanshutyagi1205]

As always, nice & informative video Shiv. Kudos for all the efforts you put on it. Waiting for your next video on SignalR.

[@Matlus]

Thank you for you comment Himanshu! Much appreciated.

[@danielvillalba4457]

Nice video Shiv, thanks a lot for the effort on explain this concepts on a very simple and easy to undertand way!

[@Matlus]

You're most welcome Daniel! Glad you're enjoying them.

[@hn3m3s1s]

Hello, really awesome quality of the video and clear voice! Really good content as well! You are very pedagogical, thank you!

[@Matlus]

Thank you! Appreciate you comment and I'm glad you like what you see/hear.

[@marcusviniciusmatiasdearru1681]

keep going sir. amazing content!

[@Matlus]

Thank you Marcus! Glad you're enjoying the content

[@assonancex]

Yeah I have really enjoyed this and your delivery is excellent. Thanks for that and keep up the good work :)

[@practicise]

Sir have you pdf notes also

[@MrJonnis13]

Super. Thanks a million

[@Matlus]

You're most welcome Johnny

[@nikhilramabhadra6052]

🤣 SNR for XML and JSON is terrible. Haven't heard that abbreviation since a long time. White (electronic) noise too. I was hoping you were going to go into SYN, SYN-ACK, SYN, packet rebuilding, sequence numbers, error correction codes, balanced wire transmission, emitters and detectors etc... Things I've forgotten since university days. 😀 I enjoyed the demo. Video on http2?

[@Matlus]

A person after my own heart Nikhil! It's been a while since I dug so deep as well, to the point where I wouldn't want to go that far :). I you SNR probably dur to my electronics background. But then decoupling, Interface, and others terms are barrowed from Electronics as well, so I figured, what the hell!

[@m.b.3488]

What an incredible fucking video... god bless you

[@amanagarwal7186]

Shiv one question regarding tcp connection. So, consider one scenario where Server got down for some reason and Client is still running. So after restarting server, will the same connection establish to send data to client or do i need to restart the client also to do further communication with server using tcp connection?

[@Matlus]

If you've programmed the client correctly, you don't need to restart the client. Let's consider a browser. If a server goes down or your internet connection drops, the browser will reconnect to the server upon re-trying. You will need to reconnect to the server and then continue the communication.

[@amanagarwal7186]

@@Matlus so that means client is not holding any connection id. Right? Idk is there any connection id concept also exist in this case? Can you please cover all these scenarios in your next video? Also with some code snippets. That will be very helpful.

[@Matlus]

@@amanagarwal7186 At the TCP level there is no connection id. But at the application level there may be. I'm not sure I understand your particular problem but I do think it is either due to the way code is written or there is something in the application (server or client) that could be an issue. I'm afraid, it's not possible to cover and nor do I know *all* these scenarios :).