[nanomsg] Re: How block wsarecv with Windows XP?
- From: Timothee Besset <ttimo@xxxxxxxxx>
- To: "nanomsg@xxxxxxxxxxxxx" <nanomsg@xxxxxxxxxxxxx>
- Date: Tue, 3 Mar 2015 09:54:41 -0800
Hello Ranier,
Do you have a test case that shows this problem? Is it encountered as part
of the normal regression tests?
Looking at the documentation, you could probably ignore/disable that flag
on XP entirely. You may want to add a loop to fill up the buffer and
basically simulate what MSG_WAITALL does.
Best,
TTimo
On Tue, Mar 3, 2015 at 4:10 AM, Ranier VF <ranier_gyn@xxxxxxxxxxx> wrote:
> Hi,
>
> src\aio\usock_win.inc, line: 454
> wflags = MSG_WAITALL;
>
> wsarecv is not supported MSG_WAITALL with TCP socket, MSDN says:
> "Be aware that if the underlying transport provider does not support
> *MSG_WAITALL*, or if the socket is in a non-blocking mode, then this call
> will fail with *WSAEOPNOTSUPP"*
>
> *With:*
> *wflags = 0;*
>
> wsarecv wont block, and return immediatly.
>
> How block wsarecv with Windows XP?
>
> best regards,
>
> Ranier Vilela
>
> Ps. Sorry, my mistake in first message.
>
Other related posts:
