Date: Sat, 24 Feb 1996 12:34:16 -0800 (GMT)
From: Orlando Andico <oandico AT eee DOT upd DOT edu DOT ph>
To: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
cc: djgpp AT delorie DOT com
Subject: Re: your mail
In-Reply-To: <9602240414.AA12184@clio.rice.edu>
Message-ID: <Pine.SOL.3.91.960224122848.2052A-100000@gollum>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Fri, 23 Feb 1996, Charles Sandmann wrote:

> There is a TCP/IP library out there, and DJ put <sys/fsext.h> behavior into
> V2 just for this purpose (so reads/writes could work to alternate devices).
> As a matter of fact, we had discussed a BSD like sockets package sometime
> in the past.  As far as timing, I can't say.  It's on my "I want it bad 
> enough to do it" list, but I am currently very short on time, so it wouldn't
> be real soon.

Forgive my hasty mail, but the TCPLIB by Martin Granell, as modified by 
Michael Leodeolter, is probably what we're talking about. The major diffs 
between it and the BSD sockets is that you can't use 
read/write/read_v/write_v on the socket; you must use read_s, etc. 

Also, there's no <netdb.h> or <arpa/inet.h> and the socket behavior is 
nonblocking. Otherwise, it looks pretty good. I just changed three lines 
of the HTTP server I'm writing for Solaris/Linux and it compiled with V2. 
(I haven't modified the read's to read_s's yet though).

Perhaps hacking this code to take advantage of <sys/fsext.h> wouldn't be 
too hard... could you point me to some docs on how to do this?

Regards;

Orly