Home/ Questions/Q 7048655
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T02:55:05+00:00

I am writing a cross-platform library which, among other things, provides a socket interface,

  • 0

I am writing a cross-platform library which, among other things, provides a socket interface, and while running my unit-test suite, I noticed something strange with regard to timeouts set via setsockopt(): On Windows, a blocking recv() call seems to consistently return about half a second (500 ms) later than specified via the SO_RCVTIMEO option.

Is there any explanation for this in the docs I missed? Searching the web, I was only able to find a single other reference to the problem – could somebody who owns »Windows Sockets
Network Programming« by Bob Quinn and Dave Shute look up page 466 for me? Unfortunately, I can only run my test Windows Server 2008 R2 right now, does the same strange behavior exist on other Windows versions as well?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I am having the same problem. Going to use

    patchedTimeout = max ( unpatchedTimepit – 500, 1 )

    Tested this with the unpatchedTimepit == 850

    • 0