Mail Archives: djgpp/1998/10/23/13:24:45
On Fri, 23 Oct 1998, Walter Moore wrote:
> George Foot wrote:
> >
> > Hello
> >
> > I recently ported a sockets application (the Libnet library, in
> > fact) to RSXNTDJ, using the Winsock. I have it working at the
> > moment, but I had to make some changes to the supplied headers.
> > If anybody else has used Winsock from RSXNTDJ successfully, I'd
> > like to know whether they had to do what I have done, or whether
> > there's an easier (read: cleaner) way.
>
> I have not been able to get my application to write to a socket
> successfully. Actually, it looks like the client just THINKS its
> connecting, but the server never sees any such connection.
Hmm. Mine definitely works.
> Nor am I using any of the select functions, though I probably
> should. But I did use the winsock.h from the MSSDK,
> with the newest patch applied in the include/mssdk directory.
>
> This client and server work on a unix machine, so I just need
> to figure out how to make it all work in the PC world.
Note that the Winsock needs special initialisation before you
can use it. Other than that (and a few compatibility defines)
your standard Berkeley sockets code should work reasonably well.
> > My last concern is that maybe Winsock 2 support is part of the
> > MSSDK. I have downloaded it, along with Doug Gale's patches,
> > but have not yet installed it. Since RSXNTDJ already had a
> > winsock.h file I assumed it was meant to support Winsock
> > programming without needing the MSSDK. Please correct me if I'm
> > wrong.
>
> according to the Bugs and missing features of RSXNTDJ 1.31,
> "* socket functions not implemented (alpha status), use WinSockets"
>
> So I'd guess you'd have to use the mssdk include files at least.
> That SHOULD clear up problems with winsock.h include file.
Oh, hmm. I wonder whether it was actually talking about Winsock
when it said `socket functions'.
> Of course, this is all hypothetical, as I do not yet have my
> own application writing to a socket successfully. I may have to
> start smaller and work my way up. The client seems to think
> its connecting, but the server is never actually being connected
> to.
I'll be uploading my source code shortly, so you could take a
look at that and try it out yourself.
--
george DOT foot AT merton DOT oxford DOT ac DOT uk
xu do tavla fo la lojban -- http://xiron.pc.helsinki.fi/lojban/lojban.html
- Raw text -