Message-Id: <1.5.4b13.32.19960426155825.006af160@oak-web.washington-ch.oh.us>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 26 Apr 1996 11:58:25 -0400
To: djgpp AT delorie DOT com
From: Daniel Pierce <ab134 AT oak-web DOT washington-ch DOT oh DOT us>
Subject: TCPIP lib - update coming..

Hi,
	The TCPIP library as it stands at the moment is not very easy to
use :P I basically adapted Michal Furmanczyk's port of wattcp to djgpp
in order to run a unix based program. As such it only required non-blocking
socket IO for TCP apps.
	I intended to add to the library over the summer, but I started 
doing a lot of programming in Linux, and so as such did not have the need
for a DOS based tcp library.
	Anyway, enough history... I've started re-porting the library, using 
a more uptodate version of the 16 bit wattcp library. After my finals (in 6
days :P) I'll be finishing the port (all things being well). What I want
to do is split the library into three interfaces:
	1) Unix type sockets, blocking and non-blocking for porting of unix
based apps to DOS
	2) The original wattcp interface.
	3) The winsock specification, which is similar to the unix sockets.

	I'm not sure what the best way to do this is. Should there be three
libraries, with header files for the three different interfaces (As some
of the functions have the same name but differing arguments and responses).
Should there be a set of defines, which rename the differing functions, such
as get_host_by_name to wattcp_get_host_by_name and unix_get_host_by_name, and
then just have one library. Or is there a better way of doing it.
	If anyone else has worked on the library, or has sample code snippets
which could be included as examples of using the library, could you please
send them to me, for inclusion in the next release. (Only a year later than
expected :P)

		Yours,

			Martin (Cramming like mad...)