Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!uwm.edu!linac!att!ucbvax!ADMIN.HumberC.ON.CA!GRAY
From: GRAY@ADMIN.HumberC.ON.CA (Kelly Gray)
Newsgroups: comp.sys.apple2
Subject: Re: Request for Comment on Kermit...
Message-ID: <91Apr18.091711edt.23337@ugw.utcs.utoronto.ca>
Date: 18 Apr 91 12:00:21 GMT
References: <hub.ucsb.edu!ucsbuxa!6500erik@UCSD.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 19

I have used Kermit on the Apple II+, and I agree, it is slow. In fact
I'd have to say that it is the slowest protocol around. It does however
have a major advantage. Kermit is the ONLY protocol I'm aware of that
can tolerate character substitutions by terminal servers. Kermit is
also highly tolerant of line noise, and doesn't mind a seven bit data
path (Xmodem REQUIRES an eight bit data path)

Kermit was written  specifically for data transfer to and from mainframes
via the terminal ports. Speed, elegance, and just about everything else
was sacrificed for RELIABILITY. Kermit may be slow, but it keeps on going
long after everything else has given up.

     <o_o>
 _________________________   ________________________________________
/                         \ /                                        \
|        Kelly Gray        |  The opinions expressed in the preceding |
|                          |  message are not guaranteed to represent |
| GRAY@ADMIN.HumberC.ON.CA |  any form of rational thought whatsoever |
\_________________________/ \_________________________________________/