C++ cross platform TCP/IP library.

[Craige]

Yes yes, I know I just posted a topic that said I am relatively new to C++, but the best way for me to learn is to do some particle exercises, and beings my life revolves around the net, the most particle program I could do would revolve around the net as well.

So, does anybody know of any good cross platform TCP/IP libraries for C++, and tutorials for that library?

[md]

*nix Sockets are standard across almost all operating systems. They are as low as you get, but they are really powerful and not at all hard to learn the basics.

Do a google for "Beej's Guide" and you should find the best guide to sockets you could ever want. Also, take a look at the cSocket class at svn://svn.nxor.org/vnet/

[r.3volved]

md wrote:

Do a google for "Beej's Guide" and you should find the best guide to sockets you could ever want. Also, take a look at the cSocket class at svn://svn.nxor.org/vnet/

Took the words right out of my mouth...er fingers...

If you prefer winsock, check the MSDN website for a breakdown of how it is used...(their example on MSDN uses EXTREMELY bad logic however, but at least it will run you through the order of steps.

When coded properly, the winsock is very quick and very solid, but alas it only works with windows. When making cross platform sockets there is a lot of #ifdef's to deal with and can make your code look pretty hideous at times.

Since you're just beginning sockets, I'd suggest starting with a single platform (window=winsock, *nix=*nix sockets) and basically get your bearing on both independantly from eachother at first. THEN combine them into a cross-platform library.

You will better understand the differences between the two, and despite what all the linux die-hards or the windows die-hards will say...it is still very important to know BOTH windows and linux platforms and their relative api's, no matter which you prefer using.

[wtd]

Boost Socket

[r.3volved]

^^

Boost owns
If you don't have the libraries installed yet, you should look into it

[Craige]

r.3volved wrote:

md wrote:

Do a google for "Beej's Guide" and you should find the best guide to sockets you could ever want. Also, take a look at the cSocket class at svn://svn.nxor.org/vnet/

Took the words right out of my mouth...er fingers...

If you prefer winsock, check the MSDN website for a breakdown of how it is used...(their example on MSDN uses EXTREMELY bad logic however, but at least it will run you through the order of steps.

When coded properly, the winsock is very quick and very solid, but alas it only works with windows. When making cross platform sockets there is a lot of #ifdef's to deal with and can make your code look pretty hideous at times.

Since you're just beginning sockets, I'd suggest starting with a single platform (window=winsock, *nix=*nix sockets) and basically get your bearing on both independantly from eachother at first. THEN combine them into a cross-platform library.

You will better understand the differences between the two, and despite what all the linux die-hards or the windows die-hards will say...it is still very important to know BOTH windows and linux platforms and their relative api's, no matter which you prefer using.

Okay, makes sence. I'll probably start with the *nix sockets, as that is the system I'll be spending most of my time on when I get my network connection set back up on it (waiting for new rogers connection before I set it up).

So if that is the case, I don't necessarily need the names of any cross platform libraries at this time.