From: Richard Dawe Newsgroups: comp.os.msdos.djgpp Subject: Re: IPC on Windows Date: Wed, 25 Oct 2000 22:31:09 +0100 Organization: Customer of Energis Squared Lines: 30 Message-ID: <39F7511D.84AD3417@bigfoot.com> References: <39F48949 DOT 3FF0CDD7 AT bigfoot DOT com> NNTP-Posting-Host: modem-154.elessar.dialup.pol.co.uk Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Trace: news6.svr.pol.co.uk 972509534 26254 62.136.185.154 (25 Oct 2000 21:32:14 GMT) NNTP-Posting-Date: 25 Oct 2000 21:32:14 GMT X-Complaints-To: abuse AT theplanet DOT net X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.17 i586) X-Accept-Language: de,fr To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Hello. Damian Yerrick wrote: > > On Tue, 24 Oct 2000 14:33:08 +0200 (CEST), Dieter Demerre > wrote: > > >bind() > >gethostbyname() > >socket() > >select() > > These functions are available in Winsock, a port of BSD sockets to > Windows. Winsock isn't a port of BSD sockets. It's a new API that is compatible in most ways with the BSD sockets API. There are some subtle and not-so-subtle differences between BSD sockets and Winsock - see the Winsock Programmers FAQ: http://www.cyberport.com/~tangent/programming/winsock/ In particular Windows and Unix do asynchronous I/O on sockets in a completely different way. Bye, -- Richard Dawe [ mailto:richdawe AT bigfoot DOT com | http://www.bigfoot.com/~richdawe/ ]