Jump to content
  • Advertisement
Sign in to follow this  
  • entries
  • comments
  • views

More IOCP woe

Sign in to follow this  
Evil Steve


Ok, so I have my socket code working to accept clients, and handly reading data.
And already it's becomming a fucking mess.

A socket can be killed from both sides of the socket manager - the network layer by the client disconnecting, and the API layer but the code calling CSocket::Disconnect(). I'm already having problems trying to get the code to nicely handle a client disconnecting. I can't be bothered trying to explain it, but basically I can't kill a socket without all of it's IO events being flushed and stuff.

Oh shit it, I'm going to get drunk.
Sign in to follow this  


Recommended Comments

There are no comments to display.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Advertisement

Important Information

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

GameDev.net is your game development community. Create an account for your GameDev Portfolio and participate in the largest developer community in the games industry.

Sign me up!