home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!rutgers!faatcrl!jprad
- From: jprad@faatcrl.UUCP (Jack Radigan)
- Newsgroups: comp.sys.amiga.datacomm
- Subject: Re: Amiga Comms (was RE: Amiga Kiosks?)
- Message-ID: <3633@faatcrl.UUCP>
- Date: 27 Aug 92 02:47:15 GMT
- References: <1992Aug21.162454.7251@TorreyPinesCA.ncr.com> <kehlet.060m@kehlet.adsp.sub.org> <rwm.714583210@atronx.OCUnix.On.Ca> <1992Aug24.193947.11784@TorreyPinesCA.ncr.com> <kehlet.06km@kehlet.adsp.sub.org>
- Organization: FAA Technical Center, Atlantic City NJ
- Lines: 24
-
- kehlet@kehlet.adsp.sub.org (Jesper Kehlet) writes:
-
- >It's also his money! If you wish to get a superior Zmodem protocol, you
- >must pay for it (hiya, Chuck!), now, would it be a good idea to make it
- >public thereafter?
-
- That's one point I disagree on, heavily.
-
- When Chuck Forsberg first released ZMODEM, one of the rationalizations for
- it being a publically documented protocol (aside from Telenet funding the
- initial development) was that proprietary schemes are "tightly bound to the
- fortunes of their suppliers".
-
- The status of ZMODEM-90 is a direct collision with that stance. Sure, he
- worked hard on tweaking a few more percentile out of the protocol, but what
- good is it now that it is a privately held specification? Well, it is
- obtainable, but at significant expense if you wish to use it in a for-profit
- venture...
-
- Anyways, the point here is that the protocol specification should be in
- the public domain, the source code for a specific implementation of the
- protocol does not, however. (sorry Russ, couldn't resist :-)
-
- -jack-
-