Timeline for What will be the behaviour of TCP in a case when application layer is changed to send small packets
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 16, 2020 at 15:41 | history | edited | Zac67♦ | CC BY-SA 4.0 |
added 111 characters in body
|
| Jan 16, 2020 at 13:40 | history | edited | Zac67♦ | CC BY-SA 4.0 |
added 9 characters in body
|
| Jan 16, 2020 at 13:38 | comment | added | Zac67♦ | @nj-ath A request is an application-layer concept, there is no such a thing on the transport layer. TCP transports arbitrary-length, bilateral streams (reordering and retransmitting packetized segments as required to reassemble the original stream) while UDP transports discrete datagrams. It seems you've got a problem with TCP's logic and possibly the API you're working with, and need to read up on those. | |
| Jan 16, 2020 at 11:59 | vote | accept | nj-ath | ||
| Jan 16, 2020 at 10:53 | comment | added | Ron Maupin♦ | @nj-ath, TCP is not message-oriented like UDP is. TCP segments streams of data, and it sends the segments, whether the data is small chunks that it collects, or large chunks that it must segment. The segments will be approximately the same size, and the segments get ordered correctly before the segment payload passes to the application.. | |
| Jan 16, 2020 at 8:46 | comment | added | nj-ath | Let us say for example an application sends ten separate requests to TCP. And one of the requests came earlier or later. Will the TCP still reorder them? Because it is a single request and TCP is supposed to give back the response to that request. (Assuming MSS is same as the data segment given by the application layer). | |
| Jan 16, 2020 at 7:30 | history | answered | Zac67♦ | CC BY-SA 4.0 |