https://bugs.freedesktop.org/show_bug.cgi?id=69526
--- Comment #6 from Pierre Ossman <[email protected]> --- (In reply to comment #4) > c327850d9e4479a0572b7baaf8dafd737586e5a1 was indeed a work-around for > pa_read() returning an error (EWOULDBLOCK) for sockets that should normally > block. > > What "documented side effect" are you talking about specifically? The > WSAEventSelect docs are long and confusing. Yeah, Microsoft's socket API is not their finest work. :) On the MSDN Library page for WSAEventSelect()[1] we can read: "The WSAEventSelect function automatically sets socket s to nonblocking mode, regardless of the value of lNetworkEvents. To set socket s back to blocking mode, it is first necessary to clear the event record associated with socket s via a call to WSAEventSelect with lNetworkEvents set to zero and the hEventObject parameter set to NULL. You can then call ioctlsocket or WSAIoctl to set the socket back to blocking mode." [1] http://msdn.microsoft.com/en-us/library/windows/desktop/ms741576%28v=vs.85%29.aspx -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug.
_______________________________________________ pulseaudio-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/pulseaudio-bugs
