Thread: Proper way to handle WSAEWOULDBLOCK

  1. #1

    Proper way to handle WSAEWOULDBLOCK

    Hi, Im writing my first multiplayer game and found a problem:
    The server sends data X times per second. If this X is bigger than 20, I start to get a lot of WSAEWOULDBLOCK messages...I could simply ignore them, but I don't know if this is correct. Some guy told me that I should check send/recv availibility more often, but I don't uynderstand what this means...

    Thx. Regards

    FunkMeister I. Wish

  2. #2
    train spotter
    Join Date
    Aug 2001
    near a computer
    WSAEWOULDBLOCK means the data did not get sent. Your response depends on the priority level of the blocked data.

    If just an screen update probably OK, particularly if using UDP.
    If not, will need to realloc your socket buffer ( or create a storage buffer for the blocked data), add blocked info to the buffer and try to resend as the block clears.
    "Man alone suffers so excruciatingly in the world that he was compelled to invent laughter."
    Friedrich Nietzsche

    "I spent a lot of my money on booze, birds and fast cars......the rest I squandered."
    George Best

    "If you are going through hell....keep going."
    Winston Churchill

Popular pages Recent additions subscribe to a feed

Similar Threads

  1. Help with setting text into LTEXT using Window Handle
    By jasperleeabc in forum Windows Programming
    Replies: 6
    Last Post: 05-08-2009, 08:18 PM
  2. Getting other processes class names
    By Hawkin in forum Windows Programming
    Replies: 3
    Last Post: 03-20-2008, 04:02 PM
  3. Direct3D problem
    By cboard_member in forum Game Programming
    Replies: 10
    Last Post: 04-09-2006, 03:36 AM
  4. Button handler
    By Nephiroth in forum Windows Programming
    Replies: 8
    Last Post: 03-12-2006, 06:23 AM
  5. Manipulating the Windows Clipboard
    By Johno in forum Windows Programming
    Replies: 2
    Last Post: 10-01-2002, 09:37 AM