Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!hellgate.utah.edu!helios.ee.lbl.gov!ucsd!hub!6500stom
From: 6500stom@hub.UUCP
Newsgroups: comp.sys.mac.programmer
Subject: Re: Communications Toolbox questions
Message-ID: <3352@hub.UUCP>
Date: 18 Dec 89 08:50:50 GMT
Sender: news@hub.UUCP
Lines: 24

>>The Comm Toolbox looks like a marvelous effort, but its metaphors seem to
>>break down more and more the farther your get from a serial line...
> 
> Yes, it looks like it should be called the "Modem Toolbox" as it stands
> now.  It simply won't work for LAN functions.  Maybe the solution is
> for Apple to hire you and me to bring it up to spec for TCP/IP....

I agree entirely.  Apple should have written an External Comm Mgr that
encompassed all of AppleTalk, serial ports and any other cards that
might be installed.  They obviously didn't think the Comm Mgr project
through very well and as a result we're going to have lots of hacks
floating around that bipass the weaknesses of the Comm Mgr.

The big missing features are background file x-fers, serial port
allocation and better support for non-modem stuff.  In short, it looks
like Apple bungled the Comm Mgr as badly as v 1.0 of the Sound Mgr.
As least the Comm Mgr isn't as bad as the first file mgr... or is it?
Its unfortunate that Apple (anyone, actually) can't get everything
right the first time.

/            Josh Pritikin             T Ignorance is bliss.           \
| Internet:  6500stom@ucsbuxa.ucsb.edu | I must be in hell.            |
| AppleLink: Josh.P                    | My room is proof that entropi |
\ GEnie:     J.Pritikin                ! exists.                       /