WSAGetLastError() and threads.
Presumably, if were running several threads each with their own sockets in, then checking the result of WSAGetLastError() could be the error produced as a result from a socket error in another thread. Or does winsock allow for this? Is there a reasonable way around this? Also, we cant really get around this by using semaphores if we''re having blocking sockets, I suppose as this would be a major resource hog in something like a multiplayer game.
Anyone care to enlighten me?
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement