Re: [Plib-devel] Networking Code

[Sam S. <sa...@sp...>]

----- Original Message -----
From: "Ben Woodhead" <be...@bg...>
To: <pli...@li...>
Sent: Tuesday, August 22, 2000 4:01 PM
Subject: RE: [Plib-devel] Networking Code


> >ACE is built upon on single core class ACE_OS, which provides a single
> Unix/POSIX like >interface to all the standard thread and
> >socket calls.
> >
> >This is mostly done in ACE_OS.h as a large bunch of #ifdef's.  I haven't
> really studied it >that much, but it might be worthwhile
> >having a look.
> >
> >(One gottcha I should point out is that almost all the higher level ACE
> applications use >
> >recv and send - not read and write (these
> >calls are supposed to be identical), with the result that ACE_OS::read and
> ACE_OS::write >
> >appear to be broken under Win2000 with ACE
> >(This might actually be problems with WinSock under Win2K I haven't
> investigated)).
>
> I did not realise that you could use recv and send and not read and write
> with TCP, I think I  read somewhere that for the TCP section I should use
> read and write, I really don't know if there is a difference but I will have
> a look at it.

Yep, recv and send can be used on TCP sockets - at least I use them without problems.

> As well I have not had much of a chance to look at winsocks so I am not
> really sure what is the best way to deal with windows but I will be looking
> at that.

Well winsock is based on the BSD socket implementation, which is what most Unixes use so these really not a lot of difference so
long as you stick to the basic calls (and winsock requires some init() and fini() calls too.)  Might be that your code already
compiles fine on Win32 once the needed headers are added.  I'll test it tonight.

> Thanks Ben
> ps Can you send me a link to where I can find ace. I don't think I ran
> across that yet.

Yeah sure:

http://www.cs.wustl.edu/~schmidt/ACE.html

Sam