Skip to main content
added 36 characters in body
Source Link
Ron Maupin
  • 101.1k
  • 26
  • 123
  • 199

For TCP and UDP, there are no clients or servers. The client/server concept is an application concept that is off-topic here.

TCP creates connections between peers, while UDP is a fire-and-forget protocol. UDP will send a datagram with no expectation that the other side even receives the datagram, and it is up to the application or application-layer protocol to provide services that TCP may offer.


There are some problems with the link you provided. For example:

enter image description here

That is completely incorrect. The UDP header is eight octets, while the TCP header is 20 to 60 octetsoctets; just the opposite of what is shown. I would not trust the site.

For TCP and UDP, there are no clients or servers. The client/server concept is an application concept that is off-topic here.

TCP creates connections between peers, while UDP is a fire-and-forget protocol. UDP will send a datagram with no expectation that the other side even receives the datagram, and it is up to the application or application-layer protocol to provide services that TCP may offer.


There are some problems with the link you provided. For example:

enter image description here

That is completely incorrect. The UDP header is eight octets, while the TCP header is 20 to 60 octets. I would not trust the site.

For TCP and UDP, there are no clients or servers. The client/server concept is an application concept that is off-topic here.

TCP creates connections between peers, while UDP is a fire-and-forget protocol. UDP will send a datagram with no expectation that the other side even receives the datagram, and it is up to the application or application-layer protocol to provide services that TCP may offer.


There are some problems with the link you provided. For example:

enter image description here

That is completely incorrect. The UDP header is eight octets, while the TCP header is 20 to 60 octets; just the opposite of what is shown. I would not trust the site.

edited body
Source Link
Ron Maupin
  • 101.1k
  • 26
  • 123
  • 199

For TCP and UDP, there are no clients or servers. The client/server concept is an application concept that is off-topic here.

TCP creates connections between peers, while UDP is a fire-and-forget protocol. UDP will send a datagram with no expectation that the other side even receives the datagram, and it is up to the application or application-layer protocol to provide services that TCP may offer.


There are some problems with the link you provided. For example:

enter image description here

That is completely incorrect. The UDP header is eight octets, whiltwhile the TCP header is 20 to 60 octets. I would not trust the site.

For TCP and UDP, there are no clients or servers. The client/server concept is an application concept that is off-topic here.

TCP creates connections between peers, while UDP is a fire-and-forget protocol. UDP will send a datagram with no expectation that the other side even receives the datagram, and it is up to the application or application-layer protocol to provide services that TCP may offer.


There are some problems with the link you provided. For example:

enter image description here

That is completely incorrect. The UDP header is eight octets, whilt the TCP header is 20 to 60 octets. I would not trust the site.

For TCP and UDP, there are no clients or servers. The client/server concept is an application concept that is off-topic here.

TCP creates connections between peers, while UDP is a fire-and-forget protocol. UDP will send a datagram with no expectation that the other side even receives the datagram, and it is up to the application or application-layer protocol to provide services that TCP may offer.


There are some problems with the link you provided. For example:

enter image description here

That is completely incorrect. The UDP header is eight octets, while the TCP header is 20 to 60 octets. I would not trust the site.

Source Link
Ron Maupin
  • 101.1k
  • 26
  • 123
  • 199

For TCP and UDP, there are no clients or servers. The client/server concept is an application concept that is off-topic here.

TCP creates connections between peers, while UDP is a fire-and-forget protocol. UDP will send a datagram with no expectation that the other side even receives the datagram, and it is up to the application or application-layer protocol to provide services that TCP may offer.


There are some problems with the link you provided. For example:

enter image description here

That is completely incorrect. The UDP header is eight octets, whilt the TCP header is 20 to 60 octets. I would not trust the site.