Path: utzoo!attcan!uunet!know!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!hayes
From: hayes@Apple.COM (Jim Hayes)
Newsgroups: comp.sys.mac.comm
Subject: Re: Telnet...TCP or NCSA ???
Message-ID: <45353@apple.Apple.COM>
Date: 4 Oct 90 02:32:46 GMT
References: <13794@slice.ooc.uva.nl> <4730@crystal9.UUCP>
Distribution: comp
Organization: Apple Computer Inc., ECO Networking Group
Lines: 33

derosa@motcid.UUCP (John DeRosa) writes in article <4730@crystal9.UUCP>:
>
>MacTCP - This feature is, at a simplistic level, a convienence for
>        the macintosh user.  MacTCP is a CDEV that allows you to 
>        set the TCP/IP information for you Macintosh in one spot,
>        i.e. the control panel, instead of within the various 
>        applications.  The advantage is that the addition of newer
>	MacTCP friendly programs will be easier as they all find their
>	network information in a common spot.  Other products that
>	use this feature are tn3270 and Gator-Mail (SMTP gateway for
>	MS Mail and QuickMail).
>

Not exactly.  MacTCP is the complete TCP/IP protocol stack developed
and supported by Apple Computer.  It is a *driver* which means it has a
standard programmatic interface and thus makes developing TCP/IP
applications much easier because the developer doesn't have to include
a home grown (and possibly buggy) TCP/IP stack.  It includes software
to perform Domain Name System host lookups as well.

Vanilla NCSA Telnet contains NCSA's own TCP/IP stack and DNS resolver.
NCSA Telnet for MacTCP uses MacTCP's stack and it's own (argh!) DNS resolver.

Developers should strive to make all their TCP/IP applications use
MacTCP thus insuring performance enhancements and upgrades appear
transparent to the application using them.


-- 
Jim Hayes, AppleTalk-TCP/IP Weenie
Advanced Technology Group, Apple Computer Inc.

Inet: hayes@apple.com		 UUCP: {amdcad|decwrl|ames}!apple!hayes