[comp.protocols.appletalk] SUMMARY: BSD sockets for Think C

kovar@ECLECTIC.COM (04/09/91)

  I originally posted a message looking a BSD socket implementation for
Think C. It took me awhile to gather all of the information together, so this
summary message was a bit delayed. My appologies to all who asked for 
information awhile back and have been waiting patiently.

  Here's what I have found:

  1) madhaus.utcs.toronoto.ca has a implementation of BSD sockets for MPW.
     Someone is currently porting this to Think C and is in the process
     of debugging it as we type. They'll probably release it sometime in
     May. This requires MacTCP.

  2) Frank Storbeck has produced some code with the following disclaimer:

	The program includes some socket related .h files from our
	UNIX-system: SUNOS-4.1 I am not allowed te redistribute them.
	Furthermore you need the file TCPPB.h which comes with the MacTCP
	distribution. You must have that, otherwise there is no .IPP driver
	available.  We use the software also for our LabVIEW software to
	get input from the network. As LabVIEW crashes when you call malloc
	we have made a hack to prevent this.

     I'll mail out this file on request. 

  3) Kinetics acquired University of Michigan's TCP/IP code and now sells
     it as TCPort. 'cept Kinetics is now Novell. Anyhow. They've not returned
     my call yet, but I believe it costs $3000, includes MacTCP, and includes
     a license to redistribute.

  

  MacTCP: It is *strongly* advised that you use MacTCP. To quote 
  Brian Bulkowski:

	Um, first thing you should beware of is people grabbing onto the IP
	frame type of the board. Because if this, it is basically impossible
	to run two IP implementations on a mac at the same time. Because you
	need more than just a socket library, you need a TCP/IP implimentation
	too. NCSA has their own TCP implementation, and if you run that you
	can 1) Only run one copy of the program in question and 2) Not have
	any other TCP implementations around. The 3 big TCPs are NCSA, MacTCP,
	and TCPort.  Of the three, the winner is definitly MacTCP. Winner here
	means market acceptance, thus less compatibility problems with other
	TCP makers.

  If I come across anything else, I'll post. Thanks again to all who
contributed!

-David