Jump to content
  • Advertisement


This topic is now archived and is closed to further replies.


winsock AND system.net.sockets.socket

This topic is 5747 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

well I have 2 questions 1: Has anyone used (or can anyone point me to a good tutorial on it) System.Net.Sockets.Socket in Visual Basic .net (7)? and 2: How do I get multiple connections to one server, do I keep an array of winsock connections, but what about the ports, it will all be on the same port...is that ok? Thank You! <- Digital Explosions -> "Discipline is my sword, faith is my shield do not dive into uncertainty, and you may live to reap the rewards" - (Unreal Championship)

Share this post

Link to post
Share on other sites
1) No
2) The only socket for which the port matters is the listening socket. Accepted connections get assigned a ''random'' port by the OS. If you get ''address in use'' errors, set the SO_REUSEADDR option (or something similar).

[ Start Here ! | How To Ask Smart Questions | Recommended C++ Books | C++ FAQ Lite | Function Ptrs | CppTips Archive ]
[ Header Files | File Format Docs | LNK2001 | C++ STL Doc | STLPort | Free C++ IDE | Boost C++ Lib | MSVC6 Lib Fixes ]

Share this post

Link to post
Share on other sites

  • Advertisement

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!