1:19 - Network Layer " decided which physical path the data will take ". Isn't it logical path? Isn't the case that Network layer/Layer 3 ( IP ) is responsible for logical addressing, while layer 2, or data link layer responsible for physical addresses ( like the Medium Access Control or MAC addresses which are 48 bit numbers resolved using ARP ? )
In case of microservices architecture, say I have a process A and process B. Now, Process A needs to continuously ask for some data from Process B. In this case, horizontal scalability issue does not come into picture. Do you think web socket communication is suitable in this scenario.?
So in a simple way, HTTP sends a request and then receives a response. Then the connection is closed. Web Sockets constantly send and receive messages and only cut off if the user/server wants to.
HTTP and Web Sockets both run on top of a TCP Connection. We cannot compare TCP with web sockets because Socket runs over TCP. TCP allows two-way communication by default but HTTP being stateless works on the request-response model. On the other hand, Sockets are stateful so they have duplex(two-way) communication.
wtf you are explaining very confusing , so http connection close but tcp connection remain wtf is that ? http is in application layer and tcp is at layer 4 so how one can be close and other is open you are confusing !!!!
![Felix "Unfair" | [Stray Kids : SKZ-PLAYER]](http://i.ytimg.com/vi/Oswujxm2Ag0/mqdefault.jpg)
Start learning Full Stack Web Development with codedamn: cdm.sh/fullstack
Love that you just keep the Ring of Power on all your content.
This is great man. Need more content like this. Understanding the different web technologies is great.
Concise and simple explanation. I love the whiteboard instead of a prepared powerpoint. It feels much easier to follow somehow.
For a long time HTTP and websocket were the same to me... Thank you for clarifying the difference
Amazing. i have my interview tmrw and this gives a quick overview. thank you
loved it, keep'em coming covering these mini topics, provides the "aha" moment.
Great explanation, i really like the letter vs. phonecall example, because it really helps to understand it 😄
1:19 - Network Layer " decided which physical path the data will take ". Isn't it logical path? Isn't the case that Network layer/Layer 3 ( IP ) is responsible for logical addressing, while layer 2, or data link layer responsible for physical addresses ( like the Medium Access Control or MAC addresses which are 48 bit numbers resolved using ARP ? )
wow crystal clear intro for me as a newbie. thx!
Good explanation on the relationship and establishment of a TCP connection, HTTP requests, and Sockets.
You made this complex concept become like ABC
very good video thank you, helped me a lot to understand websockets and also http again :)
Thanks for explaining these concepts in very simple way. I would suggest to add real use cases of these concepts so that we can relate it.
Great explanation 👍🏼
Great explanation of web sockets.
very good explanation
Very clear explanation. thanks mate
Thank you, great explanation!
Great explanation
Recently discovered your channel. You teach really good!! I wish I found this channel a few years before.
you have great knowledge
@codedamn please try to use ring light on higher angle than your camera so that we would not see that reflection of light
Great explaination...
Excellent video, very well explained, and easy to understand or refresh the protocols topic.
Thank you very much!
Now this is a quality content
So much informative , keep it up bro
✌️ 😀✌️
Very Helpful
This was very helpful!
bro tell me can we establish a ws connection with IRCTC
Nice explanation :)
Great explanation. As always!!
Thanks for explaining
Great, Informative 👍
Great video, thanks for this!
if HTTP(a protocol because hyper text transfer protocol) part of TCP (Transfer control protocol) then is web socket a protocol as well?
Wonderful video. Thank you
Great explaination please share some use cases for WS.
Great video. Thanks!
very clear and concise. Thank you !
In case of microservices architecture, say I have a process A and process B. Now, Process A needs to continuously ask for some data from Process B. In this case, horizontal scalability issue does not come into picture. Do you think web socket communication is suitable in this scenario.?
Great content and crystal clear explanation👍
Really nice video!
Well explained. Thanks! :)
Great video 🔥
Thank you for valuable content ❤️
Amazing thank you for great explanation.
Great One Sir :) :)
Any resource on how to use websocket and get authentication and authorisation done??
so is a websocket essentially a TCP connection that stays on?
Nice video, please bring the scaling web socket video 😁
I really love your videos
Thank you mehul sir
Video is full informative, thankyou for such videos. Please remove the animation (folded paper) from behind the images, it distracts concentration.
Thanks for such awesome videos, always waiting for your new videos, will be glad to get t-shirt giveaway
Great video
Light is distracted 🙂
No you are distracted by the light
So in a simple way, HTTP sends a request and then receives a response. Then the connection is closed.
Web Sockets constantly send and receive messages and only cut off if the user/server wants to.
Finally I get it.
If both TCP and Websockets establishes a two way communication, what is the difference between them?
HTTP and Web Sockets both run on top of a TCP Connection. We cannot compare TCP with web sockets because Socket runs over TCP.
TCP allows two-way communication by default but HTTP being stateless works on the request-response model. On the other hand, Sockets are stateful so they have duplex(two-way) communication.
Hey did you ever do a follow up video on scaling? Would it illogical to design a live chat for millions of people using websock?
Make a video on webhook
With project
Can you please show it in code ?
Nice
thankyou
When is it more beneficial to use web sockets ?
used in chat or messanger applications
Do you edit your own videos man?
Please provide in depth explanation, this video is not enough to get clear idea of a topic
ty
i think you re confused about what's half duplex and full duplex
COMMENTED FOR T SHIRT GIVEAWAY!! :)
To be honest, I am here for the GIVEAWAY 🤦♂️
Http protocol stateless horizontol scaling tcp connection duplex handshakes get/abc 2 way communication websocket tcp l4 dual channel stateful after handshake multiplr channels not allowed eebsocket not horizontally scalable
👍👍
Always assume a layman watching you and start
I am not trying to be picky, but the music in the background is really distracting
Sorry doesn't address the depth of what closing a channel really means and when another channel is established what are implications.
May the like be on this comment.
Audio quality is poor
wtf you are explaining very confusing , so http connection close but tcp connection remain wtf is that ? http is in application layer and tcp is at layer 4 so how one can be close and other is open you are confusing !!!!
WhatsApp use web sockets.
you explained nothing . total time waste..
you are making just fool
Great explaination , love these types of video
Thanks @codedamn
is so great
Amazing thank you for great explanation.