X-Authentication-Warning:	delorie.com: mail set sender to opendos-bounces using -f
Message-Id:	<QQprvj12751.200312060145@mr4.ash.ops.us.uu.net>
Date:	Fri, 5 Dec 2003 20:42:22 -0500 (EST)
From:	Gary Welles <gary AT wellesway DOT com>
To:	OpenDos <opendos AT delorie DOT com>
Subject:	Re: Arachne Web browser for DOS
Reply-To:	opendos AT delorie DOT com

Bud writes:

> This is a very interesting conversation.  I am working on porting Arachne
> to the Datalight TCP/IP Stack, SOCKETS.  SOCKETS is a TSR TCP/IP stack and
> has a WINSOCKv2 compatible interface.

The MS WINSOCK standard for Windows may be familiar, but that
dosen't make it the gold standard.  Success with a WINSOCK port
may be just a step away from BSD Sockets and a port to DOS (DV/X)
or perhaps DOS emulations in Unix, Linux or Mac OS/X.

-- Gary Welles

| THE BERKELEY SOCKET LIBRARY
|
| In order for applications to communicate with each other, whether
| on the same machine or different machines across a network, the Berkeley
| Socket Interface was chosen as the means to accomplish this in the
| DESQview/X environment.
|
| The reasons for this are clear. The Berkeley Socket Interface is the
| standard which other X Window systems and UNIX systems use to communicate.
| In addition, it is network independent--in fact, a network need
| not be present on a standalone system. DESQview/X uses the Berkeley
| Socket Interface 4.3, or BSD 4.3. This release includes two different
| types of communication--stream (TCP) and datagram (UDP). DESQview/X,
| through its BSD 4.3 routines, supports both of these types.
|
| DESQview/X supplies both the include files necessary to compile an
| application that uses BSD 4.3 as well as a socket library that performs
| the low level functions.  . . .
| Since the Berkeley Socket Interface is a well-defined (and expansive)
| interface, this document does not attempt to teach a user how to use
| BSD 4.3 Sockets--there is plenty of material that does this already.

- Raw text -