why it is called TCP/IP not UDP/IP

Toggle sidebar Toggle sidebar
Solution
T


i am beginning to wonder whether you are asking about just the name. as in "why is linux not called gnu/linux"?

in case you're not, the easy answer is this:

tcp and udp are two different protocols in the same suite. when you are creating a connection (a "socket") you specify which protocol you want to use for *that specific connection* (meaning the same application can use tcp in one case and udp in another) and, tcp - udp are two of the options. tcp is normally used when reliability is more important than speed, while udp is normally used for speed over reliability or when you want to apply your own management logic instead of using that provided by tcp. this is an...
Sort by date Sort by votes
T

thomasjames

Honorable
Jul 19, 2013
33
0
10,560


there most definitely is an answer, you just did not have the patience to read it. so i'll give you the ultra-short version, the "internet protocol" is is a suite, and it offers different comm methods depending on the app's design && / || requirements. tcp is one method. udp is another.
 
Upvote 0 Downvote
T

thomasjames

Honorable
Jul 19, 2013
33
0
10,560


i am beginning to wonder whether you are asking about just the name. as in "why is linux not called gnu/linux"?

in case you're not, the easy answer is this:

tcp and udp are two different protocols in the same suite. when you are creating a connection (a "socket") you specify which protocol you want to use for *that specific connection* (meaning the same application can use tcp in one case and udp in another) and, tcp - udp are two of the options. tcp is normally used when reliability is more important than speed, while udp is normally used for speed over reliability or when you want to apply your own management logic instead of using that provided by tcp. this is an oversimplification of course, but if you want more info, there's plenty of it around.

as an easy example, a multiplayer networked game, or a video application would favor use of udp to transfer data at the best possible speed and either tolerating transmission errors or implementing error detection and correction at the application level, while a remote data access app would tend to favor tcp and have guaranteed safe delivery of the data. once again, they are oversimplifications, it's just to give you an idea.

so i suppose that the answer to your last question is no, they are the same networking model but offering different features.
 
Upvote 0 Downvote
Solution
O

oudmaster

Distinguished
Jul 26, 2013
330
0
18,780
thanks a lot
now it is clear

actully I was confused because of the name only,
I was thinking if TCP and UDP are different protocols, and there is TCP/IP, then there must be a UDP/IP.
otherwise they will combine the name as Internet Protocol Suite


 
Upvote 0 Downvote
T

thomasjames

Honorable
Jul 19, 2013
33
0
10,560


ok. i suppose it's just a shorthand really, we always called it "tcp" or "tcp/ip" as it's shorter and more convenient than saying "internet protocol", although in my experience people occasionally did call it internet protocol, which as an aside also does not verbally commit you to actually using tcp.
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom