The setsockopt and getsockopt API diffs from BSD socket and WSA one

[dragonation]

The optval of SO_RCVTIMEO and SO_SNDTIMEO is a pointer to DWORD, not a pointer to struct timeval in Windows SDK.

ref:

• getsockopt on MSDN
• setsockopt on MSDN

[mnunberg]

This looks fine to me, though we don't ever use getsockopt in hiredis code

[dragonation]

This looks fine to me, though we don't ever use getsockopt in hiredis code

But we use setsockopt, which will cause the real timeout divided by 1000 in windows, if we connect redis server with a specified timeout, and usually it will make the connection very unstable when testing the new windows port of hiredis.

[mnunberg]

const struct timeval *tv = optval; eliminate casting plz

[dragonation]

Did it

[mbitsnbites]

I suggest that #663 is merged before this PR since it adds Travis builders for MinGW and MSVC.

If this branch is rebased on master after the merge of #663, we get CI checking of the Windows code.

[mbitsnbites]

This looks fine to me, though we don't ever use getsockopt in hiredis code

Actually, it's used here: https://github.com/redis/hiredis/blob/master/net.c#L294, although only for SOL_SOCKET, SO_ERROR. However I think it's wise to have a correct implementation in sockcompat.c in case someone decides to use it later.

[michael-grunder]

Is this safe to merge? A few people have been having timeout related issues in Windows.