Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <3A830BE8.E9B6D936@phekda.freeserve.co.uk>
Date: Thu, 08 Feb 2001 21:13:12 +0000
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.17 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: DJGPP newsgroup <djgpp AT delorie DOT com>
CC: Wojciech Galazka <wojciech DOT galazka AT polkomtel DOT com DOT pl>,
        libsocket Mailing List <libsocket AT egroups DOT com>,
        Ken Doyle <kdoyle AT ihug DOT com DOT au>
Subject: Re: Ending development of libsocket
References: <3A745502 DOT 497CA8DF AT phekda DOT freeserve DOT co DOT uk> <95ngpf$bk9$1 AT pippin DOT nask DOT waw DOT pl> <9791-Tue06Feb2001104746+0200-eliz AT is DOT elta DOT co DOT il> <95shqp$ac$1 AT pippin DOT nask DOT waw DOT pl>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp AT delorie DOT com

Hello.

Wojciech Galazka wrote:
> Ok, I got the idea. What is needed is a socket library that provides
> * TCP
> * UDP
> for socket() call
> that 's working under Win 9x/ME (= under Winsock 2.0)

Yes, exactly. AFAIK Windows ME implements its networking drivers as DLLs
rather VxDs. I suspect that libsocket will not work it.

Damian Yerrick, did you test libsocket with Windows ME? I sent you test
programs a while back, but got no response. Did you receive my test
programs?

> Ideally this library should rely on services provided by MS TCP/IP stack
> that comes with Windows
> so it implies either
> * wsock2.vxd
> * TDI API (coda.vxd)
> and IPv6 if Windows 9x/ME provides its own IPv6 stack

IPv6 is not available for Windows '9x. Microsoft is unlikely to do IPv6,
from what I've heard. An experimental IPv6 stack is available for Windows
NT, maybe Windows 2000 too (see http://www.research.microsoft.com/ and
follow links).

I think IPv6 can wait. It's not widely used (yet). Also, if we support
IPv6, then the DNS code will need a lot of work, since it does not support
IPv6-extensions to DNS.

> Direct access to lower levels of OSI layers (IP,ICMP,raw sockets) is not
> as much relevant at this moment
> How about select() and poll() ?

select() is already supported, but may be a bit buggy. I've never had
problems, but other people may have had problems with select() and dial-up
connections.

> I'll check the latest version of libsocket sources and the bug report to
> see if we can stay with wsock2.vxd and/or benefit from using coda.vxd

I'm not sure what you mean here. libsocket already uses Coda's SOCK.VXD to
work with Winsock 2. I have some work done for WSOCK2.VXD support in my
local CVS, but it needs work.

> The case with Windows NT is much clearer, once the CygWin team gets its
> version of Unix sockets to work we can make a simple stub library tthat
> calls that implementation.

How are they implementing Unix domain sockets? libsocket has a basic
implementation. It would be good if DJGPP & Cygwin could interoperate.

Bye,

-- 
Richard Dawe <richdawe AT bigfoot DOT com> http://www.bigfoot.com/~richdawe/ 

"The soul is the mirror of an indestructible universe."
--- Gottfried W. Leibniz