Welcome, Guest. Please login or register. Did you miss your activation email?

Author Topic: When sending with a TcpSocket in non blocking mode, status NotReady is returned  (Read 1981 times)

0 Members and 1 Guest are viewing this topic.

Alidaco

  • Newbie
  • *
  • Posts: 5
    • View Profile
My previous question was very vague. After doing more digging into my problem, I realized that in non-blocking mode, after many successive packet sendings, the packets were no longer sent and the send function began to return status "NotReady". I thought that I might be "overloading" the socket by doing so much so quickly, so I added some code to delay for 1 second after I got the NotReady status to let it "catch up". Sorry if that course of action seems stupid, but I'm trying my best to understand what's going on here. Regardless, that didn't help, and after the first failure, ever successive call also returns "NotReady". What do you guys think would cause a socket to repeatedly say that it's not ready after sending quite a few packets correctly in quick succession? I'm totally baffled! I hope one of you can help. I look forward to your responses, and thank you for reading!