home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!stanford.edu!bcm!lib!oac2
- From: cshotton@oac.hsc.uth.tmc.edu (Chuck Shotton)
- Newsgroups: comp.sys.mac.programmer
- Subject: Re: MacTCP (UDP) questions
- Message-ID: <cshotton-200892090749@oac2.hsc.uth.tmc.edu>
- Date: 20 Aug 1992 14:12:44 GMT
- References: <1992Aug19.173303.14543@vax5.cit.cornell.edu> <2541@tau-ceti.isc-br.com>
- Sender: usenet@lib.tmc.edu
- Followup-To: comp.sys.mac.programmer
- Distribution: comp
- Organization: Academic Computing
- Lines: 27
- Nntp-Posting-Host: oac2.hsc.uth.tmc.edu
-
- In article <2541@tau-ceti.isc-br.com>, jimc@tau-ceti.isc-br.com (Jim
- Cathey) wrote:
- >
- > In article <1992Aug19.173303.14543@vax5.cit.cornell.edu> tcd@vax5.cit.cornell.edu writes:
- > > I am working on an application that needs to transfer a continuous,
- > >high volume stream of data from one Macintosh to another. Because we
- > >can tolerate some amount of data loss/corruption it seemed like UDP
- > >would be a better choice than TCP.
- >
- > Mac-to-Mac? Does anybody remember Appletalk? Y'know, the networking
- > protocol built into _every_ Mac since '84? Why not use that?
- >
- > Enquiring minds want to know...
- >
-
- Perhaps it's one of those "facist" networks that only allows TCP/IP
- traffic? Like the Internet. :) Most big networks these days aren't built on
- LocalTalk cables and for Ethernetted Macs, MacTCP is usually easier to
- write code for than AppleTalk. ADSP contains a lot of TCP/IP functionality,
- but that does no good in an IP-only environment.
-
- --_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
- Chuck Shotton |
- Ass't Director, Academic Computing | "This space for rent."
- UT Health Science Center Houston |
- cshotton@oac.hsc.uth.tmc.edu |
- _-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-
-