This is the mail archive of the cygwin-patches@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: recvfrom / sendto patch


"Corinna Vinschen" <cygwin-patches@cygwin.com> wrote:
>
> On Sun, Aug 11, 2002 at 02:25:36PM +0100, Conrad Scott wrote:
> >
> > Again, moving slowly towards my readv/writev patch, here's a
> > little patch to simplify the fhandler_socket sendto / recvfrom
> > code.
> >
> > SUSv3 says that recvfrom, recv, and read are all equivalent on
> > sockets if no flags or addresses etc. are provided (and ditto
for
> > sendto, send, and write).  So, this patch makes that true,
partly
> > by removing some methods and making others just delegate to
each
> > other as appropriate.  In detail:
>
> Did you test that?  Is that also true for WinSock?

Sorry, I didn't add all my usual disclaimers.  Here goes:

Yes, tested w/ both connection-orientated and connectionless
sockets (the latter both w/ and w/o the client having called
connect) in both blocking and non-blocking states on win2k (my
win98 box is in bits right now).  I've not tested under winsock1
as I'm unclear how to do so (pointers welcomed).

I've also checked the documentation for both winsock 1 & 2: the
manual pages on MSDN are self-contradictory [sic], but factoring
out the documentation idiocies, they claim to work in an
equivalent way to the SUSv3 interfaces.

I'm using these patches now with my usual test programs +
XEMacs/gnuserv + cvs etc.

HTH,

// Conrad




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]