Mail Archives: djgpp/1998/07/22/00:12:05
On 21 Jul 98 at 22:23, Mandr wrote:
> Chuck Busby (scrcrow AT pacbell DOT net) wrote:
> > On Sun, 19 Jul 1998 13:00:30 -0700, Nate Eldredge <nate AT cartsys DOT com>
> > wrote:
>
>
> > >The name escapes me, but I'm fairly sure there's at least one such beast
> > >in the v2tk/ directory at the place you got DJGPP.
>
> > was it LibSocket ?
>
> I've downloaded another one named WSOCK. Haven't used it though.
> There aren't a lot of documentation on WSOCK, I only know that it also
> uses the wsock.vxd etc. (WinSock DOS backdoors) to access winsock.
>
> Anyone knows the diff and limitations on these packages?
WSOCK is C++-based, giving you a class system for accessing the
socket functions. Libsocket offers the standard socket functions for
you to call, and also uses djgpp's filesystem extension capability to
allow you to use filing functions like `write' on sockets as well as
files, so is probably a better choice if you want your code to port
nicely to Unix and other platforms. I've written a simple (smaller)
library based on WSOCK, which is a conversion to straight C and to
the standard socket interface, almost. It's not complete, and may
not be quite in line with BSD; I just wanted something that was
sufficient. If you want compatibility, go for libsocket.
All of these work only when your program is run in a DOS box under
Windows 95, using Winsock 1.x. They don't work with Winsock 2 (in
particular, I don't think they work under Windows 98, which I tihnk
uses Winsock 2 by default).
You should be able to get what you want from any of these packages,
bearing in mind the limitations mentioned in the above paragraph.
They all work in almost exactly the same way; I think it's just a
matter of taste which you prefer.
--
george DOT foot AT merton DOT oxford DOT ac DOT uk
- Raw text -