Winsocket2
-
Hey guys, Im working with winsocket in one of my projects and I have some questions regarding Windows Sockets. I see that it is used to send data over the TCP/ IP network protocol but why is it specifically called Windows socket? If I try running two different simulations which interact with one another over a network, do both of the simulations have to be running on the WINDOWS OPERATING SYSTEM? If anyone has any links that can give me the basic understanding of what goes on in the Windows Socket it would be greatly appreciated Thanks, Jay :)
-
Hey guys, Im working with winsocket in one of my projects and I have some questions regarding Windows Sockets. I see that it is used to send data over the TCP/ IP network protocol but why is it specifically called Windows socket? If I try running two different simulations which interact with one another over a network, do both of the simulations have to be running on the WINDOWS OPERATING SYSTEM? If anyone has any links that can give me the basic understanding of what goes on in the Windows Socket it would be greatly appreciated Thanks, Jay :)
WinSock is just the library name. It is basically Microsoft's implementation of the Berkeley sockets that are used on *Nix systems. From a development point of view, there is very little different in the way of method calls, arguments, etc (outside of initializing and freeing the library). When using it, you can communicate with anything that talks TCP/IP, regardless of the OS. Just make sure you keep byte-ordering in mind when programming. If you decide to become a software engineer, you are signing up to have a 1/2" piece of silicon tell you exactly how stupid you really are for 8 hours a day, 5 days a week Zac
-
Hey guys, Im working with winsocket in one of my projects and I have some questions regarding Windows Sockets. I see that it is used to send data over the TCP/ IP network protocol but why is it specifically called Windows socket? If I try running two different simulations which interact with one another over a network, do both of the simulations have to be running on the WINDOWS OPERATING SYSTEM? If anyone has any links that can give me the basic understanding of what goes on in the Windows Socket it would be greatly appreciated Thanks, Jay :)
Jay03 wrote:
If I try running two different simulations which interact with one another over a network, do both of the simulations have to be running on the WINDOWS OPERATING SYSTEM?
No. That's the beauty of TCP. Neither end has to be concerned with the other (e.g., Windows <-> Unix <-> OS/400). They just both have to speak the same language. This is a somewhat simplified explanation. See here for more on TCP. See here for more on the OSI model.
"Money talks. When my money starts to talk, I get a bill to shut it up." - Frank
"Judge not by the eye but by the heart." - Native American Proverb
-
Hey guys, Im working with winsocket in one of my projects and I have some questions regarding Windows Sockets. I see that it is used to send data over the TCP/ IP network protocol but why is it specifically called Windows socket? If I try running two different simulations which interact with one another over a network, do both of the simulations have to be running on the WINDOWS OPERATING SYSTEM? If anyone has any links that can give me the basic understanding of what goes on in the Windows Socket it would be greatly appreciated Thanks, Jay :)
-
Hey guys, Im working with winsocket in one of my projects and I have some questions regarding Windows Sockets. I see that it is used to send data over the TCP/ IP network protocol but why is it specifically called Windows socket? If I try running two different simulations which interact with one another over a network, do both of the simulations have to be running on the WINDOWS OPERATING SYSTEM? If anyone has any links that can give me the basic understanding of what goes on in the Windows Socket it would be greatly appreciated Thanks, Jay :)