Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!usc!apple!han
From: han@Apple.COM (Byron Han)
Newsgroups: comp.sys.mac.comm
Subject: Re: Comm Toolbox TCPtool documentation
Message-ID: <50530@apple.Apple.COM>
Date: 20 Mar 91 18:21:35 GMT
References: <9263@etsu.CMI.COM> <1991Mar15.033323.19357@ux1.cso.uiuc.edu> <9288@etsu.CMI.COM>
Organization: Apple R&D - Networking & Communications
Lines: 24

In article <9288@etsu.CMI.COM> kevinh@cmi.com (Kevin Hegg) writes:
>In article <19357@ux1.cso.uiuc.edu>  dorner@pequod.cso.uiuc.edu (Steve 
>Dorner) writes:
>> I would suggest you make your application switchable between MacTCP
>> and the Comm Toolbox.  This will save your MacTCP users from having to
>> deal with the Comm Toolbox until a few more kinks get ironed out.
>
I would strongly urge you to get some info on the TCP/IP connection tools
that different folks put out (like the advanced software concepts TCPack tool)

CommToolbox is not perfect - it is an evolving product that is constantly 
being improved.  But it does provide a solid developer base platform
for different applications to be built upon - like MacX, MacTerminal, 
Versaterm, PacerTerm, the terminal tools (TTY, VT102, VT320, IBM 3278), 
file transfer tools (Text, XMODEM, KERMIT, ZMODEM), connection tools 
(Serial, Modem, ADSP, LAT, DECNet, SNA, X.25, TCP/IP)


-- 
Byron Han, CommToolbox Emir       Changing the world, one connection at a time
Apple Computer, Inc.              --------------------------------------------
20525 Mariani Ave, MS: 35CP       Internet: han@apple.COM
Cupertino, CA 95014               UUCP:{sun,voder,nsc,decwrl}!apple!han
ATTnet: 408-974-6450              Applelink:HAN1   HAN1@applelink.apple.COM