Thanks for the overview, that's a good starting point for teaching. I just regret that you need to wait for the end of the article to part a little bit from the OSI model.
These days everything goes through HTTP, that is WebSocket, WebRTC or even DNS. To me, HTTP fits the shoes of the transport layer, even though it uses a transport itself!
Also about UDP, you're saying that it's unreliable but in the end no one really cares about UDP per se. Instead, that's the opportunity to implement a different mechanism on top of it with little overhead. That's kind of the API to implement your own TCP that fits your own requirements. Just saying this after implementing a few things over UDP and figuring that you end up doing a lot of things manually :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for the overview, that's a good starting point for teaching. I just regret that you need to wait for the end of the article to part a little bit from the OSI model.
These days everything goes through HTTP, that is WebSocket, WebRTC or even DNS. To me, HTTP fits the shoes of the transport layer, even though it uses a transport itself!
Also about UDP, you're saying that it's unreliable but in the end no one really cares about UDP per se. Instead, that's the opportunity to implement a different mechanism on top of it with little overhead. That's kind of the API to implement your own TCP that fits your own requirements. Just saying this after implementing a few things over UDP and figuring that you end up doing a lot of things manually :)