From: "Wojciech Galazka" Newsgroups: comp.os.msdos.djgpp Subject: Re: Ending development of libsocket Date: Wed, 7 Feb 2001 23:22:10 +0100 Organization: NASK - www.nask.pl Lines: 36 Message-ID: <95shqp$ac$1@pippin.nask.waw.pl> 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> NNTP-Posting-Host: wawhsa-236.dial.plusgsm.pl X-Trace: pippin.nask.waw.pl 981584540 332 212.2.98.236 (7 Feb 2001 22:22:20 GMT) X-Complaints-To: usenet AT nask DOT pl NNTP-Posting-Date: Wed, 7 Feb 2001 22:22:20 +0000 (UTC) X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 X-Newsreader: Microsoft Outlook Express 4.72.2106.4 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eli Zaretskii wrote in a message <9791-Tue06Feb2001104746+0200-eliz AT is DOT elta DOT co DOT il>... > >I'd say that it needs to support Windows 9X and ME as its primary >target. Plain DOS already has a solution, and I'm guiessing that >making libsocket work on NT and W2K is an entirely different ball >game. 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) 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 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() ? 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 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.