Xref: utzoo comp.sys.mac.programmer:13193 comp.protocols.tcp-ip:10582
Path: utzoo!attcan!uunet!samsung!usc!snorkelwacker!bloom-beacon!eru!luth!sunic!bmc!bio.embnet.se!mats
From: Mats.Sundvall@bio.embnet.se (Mats Sundvall)
Newsgroups: comp.sys.mac.programmer,comp.protocols.tcp-ip
Subject: Re: Mac TCP--Info??
Message-ID: <41.25fea6e7@bio.embnet.se>
Date: 14 Mar 90 19:17:43 GMT
References: <7990@tank.uchicago.edu> <39441@apple.Apple.COM>
Organization: Embnet node in Sweden, Biomedical Center, University of Uppsala, Sweden
Lines: 29

In article <39441@apple.Apple.COM>, hayes@Apple.COM (Jim Hayes) writes:
> asl2@tank.uchicago.edu (Aaron "Fish" Lav) writes:
> Reality:
> 
> 	Writing your first program using MacTCP is like writing your first
> 	BSD UNIX client/server-- It hangs, it crashes, it misbehaves.  But
> 	once you perfect it, re-using your code is simple provided you put
> 	some thought into its design.
> 
> 	If you are going to use it, I recommend Object Pascal or
> 	C++.  Make "connection objects" in which you create instances of
> 	TCP or UDP "connections" that have "read" and "write" methods.
> 	It gives you reusable code and makes good cognitive sense.  If
> 	you're not into objects, traditional methods work well too.
> 

So, do I have to write the connection objects myself, or has anyone
done it?

> 
> -- 
> Jim Hayes, TCP/IP Weenie
> Advanced Technology Group, Apple Computer Inc.
> 
> Inet: hayes@apple.com		 UUCP: {amdcad|decwrl|ames}!apple!hayes

	Mats Sundvall
	University of Uppsala
	Sweden