I have been trying to learn the basics of winsock stuff but none of the books I looked in were helpful on this topic. Can anyone tell me a good book or other source for help with winsock connection stuff?

What_language?

winsocks, my guess some type of VB?

What? C++ doesn't use winsock? ::)

[quote author=DarkMinion link=board=17;threadid=1688;start=0#msg12864 date=1056496594]
What? C++ doesn't use winsock? ::)
[/quote]

Nobody calls them "winsocks" in C, just "sockets."

Really? I suppose that's why most of the socket API functions start with "WS", which stands for "winsock". Please Camel, you make it too easy...

He has a point though...in VB the actual object you put on the form is called a "Winsock," isn't it?

In C++ (and I know you know this, DM :P) you declare it as a socket.

But you still #include winsock2.h!

Yes, they both eventually use the winsock api, which uses sockets. The socket your declare is a socket, but you need winsock to play with it.

I didn't say it is incorrect to call them winsocks in C++; it's perfectly correct. However, nobody (that I know at least) puts the extra three letters in because, unless one is trying to specify the difference between the two, it's practically redundant.

I do, and you know me. If I'm talking about linux or general sockets, I call them sockets. But if I'm talking about using them in windows, I call it winsock :)

[quote author=iago link=board=17;threadid=1688;start=0#msg12947 date=1056583816]
I do, and you know me. If I'm talking about linux or general sockets, I call them sockets. But if I'm talking about using them in windows, I call it winsock :)
[/quote]

There is no spoon!

Alrighty, from now on I will consistently say "Berkeley sockets." :P

[quote author=Zakath link=board=17;threadid=1688;start=0#msg12974 date=1056593933]
Alrighty, from now on I will consistently say "Berkeley sockets." :P
[/quote]

I doubt that highly.

Berkeley doesn't quite fully encapsulate the true name. BSD Sockets or more precisely, Berkeley Software Distribution Sockets. So, if you want to start calling them by their full names:

Windows Sockets
Berkeley Software Distribution Sockets

Now, if people start pasting those full names into posts, somebody needs to grab either the riffle or whip. I don't think anybody wants to read a post where Berkeley Software Distribution Sockets amounts for more than 50% of the entire post. That's the reason for having TLA's (three letter acroynms) and abbreviations.

Winsock
BSD sockets

furthermore, Winsock is actually MS's slight deviation of standard technology which they proceeded to name after their own software. (no suprised there eh?) It actually should be named something like Windows BSD sockets or MSBSD sockets. Oh god that would be sacreligous though. That is why in general it is best to refer to all forms and derivations of BSD sockets as just plain sockets.