Udp is message-oriented. Why is tcp message-oriented?

Udp is message-oriented. Why is tcp message-oriented? In view of this problem, this article introduces the corresponding analysis and answers in detail, hoping to help more partners who want to solve this problem to find a more simple and feasible way.

This starts with the characteristics of their work:

UDP is message-oriented, and the sender's UDP does not merge or split the messages handed over by the application layer, but adds a header to it and gives it to the lower network layer, that is, no matter how long the messages are given to the UDP by the application layer, it sends them one at a time. On the other hand, the receiver directly removes the first part after receiving it, and gives it to the upper application layer to complete the task. Therefore, it needs the application layer to control the size of the message.

TCP is oriented to byte flow. It sends the data handed over from the application layer as an unstructured byte stream, which can be imagined as a pipeline. The sender TCP will put the data into the "reservoir" (cache area) and send it when it can be sent, and wait if it can not be sent. TCP will determine the size of each message segment according to the current congestion state of the network.

This is the answer to the question about why udp is message-oriented and why tcp is oriented to byte flow. I hope the above content can be of some help to you. If you still have a lot of doubts to be solved, you can follow the industry information channel for more related knowledge.