Which Sockets Library

I'm learning sockets programming now, and I've done everything in Java so far for simplicity's sake. I want to actually make a real program now using C++, so I need to select a sockets library.

I have been using wxWidgets for my GUI. Should I just use the socket functions included in wxWidgets? Apparently it wraps the socket functions that the OS/Environment uses.

Or, is there a better library? Is there one that will work on Windows, Linux, Mac OS[X], OpenBSD, etc....?

I don't want to have to rewrite my programs from scratch for each OS. If I don't use wxWidgets, what I usually do is write the libraries and use them in each OS version, then I write the GUI for that OS and incorporate those libraries (and I basically JUST have to write a GUI).

What library should I use?


Is this one any good? --> http://www.libsockets.net/
How about the BSD Socket library (is there a port for Windows?)

I would suggest using raw sockets. BSD on *nix machines, and winsock on windows. The differences between the two are very small, so porting between platforms takes very little time.

I would say use the wxWidgets library first - if it seems to perform poorly you can try something else.

Quote:

---

Originally Posted by ChadJohnson

I've done everything in Java so far for simplicity's sake. I want to actually make a real program now

---

*sigh* :rolleyes:

As for the question, aren't the socket functions used in most C programs fairly standard?

Is there a standard C library for sockets? I haven't really looked...

the C standard doesn't specify any socket/networking specification per se, but the BSD socket library has become the de facto standard for socket programming. suprisingly enough (not!) Microsoft implemented their own version that made some minor modifications plus added quite a few extensions. the MS header you'll need is 'winsock.h', for Unix/Linux I think it's 'sys/socket.h'. you'll also need to direct your linker to the actual code of the library, and that will be completely dependant on the compiler (ie: for Bloodshed-Dev it's in 'libwsock32.a'). there are numerous socket tutorials on the net in C/C++ (including Beej's guide) that will help get you started, too. the bottom line is: as long as you stick to the BSD-style functions (and avoid the MS ones), you'll be almost 100% portable.

>>the MS header you'll need is 'winsock.h'
Actually, I think it's 'winsock2.h' unless you're programming for Windows 3.1...

its only winsock2.h if you need winsock 2 functions... good old 1.1 still works fine under NT5+ and iirc most of the winsock2 stuff doesnt fit well with bsd sockets anyway

>>most of the winsock2 stuff doesnt fit well with bsd sockets anyway
True, I suppose that would be a problem for the OP. But it contains all the 1.1 features anyways, and allows you to use winsock 2 functions if you so desire.