Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!apple!apple.COM!han From: han@apple.COM (Byron Han, Project Scapegoat) Newsgroups: comp.sys.mac.programmer Subject: Re: Communications Toolbox questions Message-ID: <5894@internal.Apple.COM> Date: 20 Dec 89 17:33:14 GMT Sender: usenet@Apple.COM Organization: Apple Computer, Inc. - N&C Lines: 26 References:<9125@hoptoad.uucp> <36869@apple.Apple.COM> <9188@hoptoad.uucp> <37028@apple.Apple.COM> <9223@hoptoad.uucp> <37200@apple.Apple.COM> <9325@hoptoad.uucp> <898@excelan.COM> In article <898@excelan.COM> brianb@kinetics.com (Brian Bulkowski) writes: > at least in the TCP world, > because it's too simple and the state of the art (InterCon's Connect II, > Novell/Kinetics' HostAccess, etc. etc.) has > gone far beyond what the CommTB will offer without significant design > changes. Agreed! The goal of the Connection Manager is to provide applications with an interface to an abstracted concept of a connection to maximize its protocol independence. If I were to write an application to only use ADSP or only use TCP/IP, I would write directly to the driver API's. If I were to write an application to transparently access SNA, DECnet, LAT, ADSP, or TCP/IP protocols, I would use the Connection Manager API. CommToolbox is not a panacea by any stretch of the imagination... +-------------------------------------------------------------------------+ | Disclaimer: Apple has no connection with my postings. | +-------------------------------------------------------------------------+ Byron Han, CommToolbox Designer "DeAnza 3 - R.I.P. - 10/17/89 5:04PM" Apple Computer, Inc. -------------------------------- 20525 Mariani Ave, MS 69L Internet: han@apple.COM Cupertino, CA 95014 UUCP:{sun,voder,nsc,decwrl}!apple!han -------------------------------- GENIE:BYRONHAN CompuServe:72167,1664 ATTnet: 408-974-6450 Applelink:HAN1 HAN1@applelink.apple.COM ---------------------------------------------------------------------------