Newsgroups: comp.protocols.tcp-ip
Path: utzoo!henry
From: henry@zoo.toronto.edu (Henry Spencer)
Subject: Re: Beginner's info TCP & UDP
Message-ID: <1990Jul17.221845.4127@zoo.toronto.edu>
Organization: U of Toronto Zoology
References: <81247@srcsip.UUCP> <Jul.16.21.14.16.1990.26321@athos.rutgers.edu>
Date: Tue, 17 Jul 90 22:18:45 GMT

In article <Jul.16.21.14.16.1990.26321@athos.rutgers.edu> hedrick@athos.rutgers.edu (Charles Hedrick) writes:
>People tend to use UDP where (1) they plan to be making isolated
>queries... (2) they need more
>performance than they think they can get from TCP...

Doesn't it also get some use for things like packet voice, where timely
unreliable delivery is better than unpredictably-delayed reliable
delivery?

Agreed that the basic answer is "use TCP unless you have a very good
reason for UDP".  If nothing else, it's much easier to get a high-quality
implementation by using a pre-built one than by building it yourself.
-- 
NFS:  all the nice semantics of MSDOS, | Henry Spencer at U of Toronto Zoology
and its performance and security too.  |  henry@zoo.toronto.edu   utzoo!henry
