1. what is UDP?
2. i know its a protocal, then what differ it from tcp/ip?
3. is it better than tcp/ip and why?
sorry, im a noob at this
Name:
Anonymous2005-01-31 6:47
there is this thing called the internet, included within is a system called the world wide web
it contains information, there are even these things called search engines
the main difference between udp and tcp is that tcp establishes a stream and udp uses standalone datagrams
go read about the protocols for the details
Name:
Chouzan2005-01-31 7:21
UDP essentially bridges the connection between the application and network layers. VOIP applications and streaming technology found in media players make use of UDP as they only require simple instructions compared to TCP and most other transport layers.
Name:
Anonymous2005-01-31 8:02
lol udp (user datagram protocol) is basically a description for custom protocols being tunneled over the internet protocol. The difference between udp and tcp is that tcp requires a stream which initialted by a three way hand shake (client tcp syn > server tcp ack, tcp syn > client tcp ack > connection established) each tcp stream require a port for both the server and the client to be allocated. further more, each packet being delivered will have a seuqence number so if one packet didn't come through, the client can request that packet again. now with udp, you can allocate ports for data transmission, but you don't really have to. basically it is just custom packets over ip, you can basically put anything in the packet after the IP header and udp ID. This however creates some problems with packet forwarding (NAT) and network routing if didn't configure your router to handle such packets. UDP is not better than tcp in the sense there is really no network traffic control unless you write it yourself. But as a programmer, you get more freedom in constructing how the network works if you use udp. further more, udp has a lot less required packet header than tcp. so it potentially can transfer more data than tcp. so in this sense it is no worse than tcp either. that's why we see it co-existing with tcp today.
Name:
Anonymous2005-01-31 8:23
btw the osi layer description is stupid, most programmers don't use half of them in coding their programs (or rather, don't give a rat's ass about half of them). it is basically there to allow the business people to see how things work without having to explain in code terms. for example, for a coder, you worry about ip > tcp > http > data... in osi terms, you have to worry about wire > ethernet > ip > tcp > one missing layer (incompassed by tcp and http) > http > browser now why would you do that unless you are building a whole network from ground up specifically for your needs? most of the protocols we use today do not use all seven layers either, some use 4, some use 6... if you ever get your hands on a osi layer vs protocol chart, you can see, not a single one uses all seven. can you imagine? network packets with 6 packet headers... that's gonna eat half of your bandwidth for nothing.