old-www/LDP/nag/node14.html

42 lines
1.8 KiB
HTML

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<!--Converted with LaTeX2HTML 96.1-c (Feb 29, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds -->
<HTML>
<HEAD>
<TITLE>The User Datagram Protocol</TITLE>
</HEAD>
<BODY LANG="EN">
<A HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="contents_motif.gif"></A> <BR>
<B> Next:</B> <A HREF="node15.html">More on Ports</A>
<B>Up:</B> <A HREF="node7.html">TCP/IP Networks</A>
<B> Previous:</B> <A HREF="node13.html">The Transmission Control Protocol</A>
<BR> <P>
<H2><A NAME="SECTION003370000">The User Datagram Protocol</A></H2>
<A NAME="introtcpipudp"></A>
Of course, TCP isn't the only user protocol in TCP/IP networking.
Although suitable for applications like rlogin, the overhead
involved is prohibitive for applications like NFS. Instead, it uses a
sibling protocol of TCP called UDP, or <em>User Datagram Protocol</em>.
Just like TCP, UDP also allows an application to contact a service on a
certain port on the remote machine, but it doesn't establish a
connection for this. Instead, you may use it to send single packets to
the destination service-- hence its name.
<P>
Assume you have mounted the TeX directory hierarchy from the
department's central NFS server, galois, and you want to view a
document describing how to use LaTeX. You start your editor, who
first reads in the entire file. However, it would take too long to
establish a TCP connection with galois, send the file, and release
it again. Instead, a request is made to galois, who sends the file
in a couple of UDP packets, which is much faster. However, UDP was not
made to deal with packet loss or corruption. It is up to the
application-- NFS in this case-- to take care of this.
<P>
<HR>
<P><ADDRESS>
<I>Andrew Anderson <BR>
Thu Mar 7 23:22:06 EST 1996</I>
</ADDRESS>
</BODY>
</HTML>