QNativeSocketEngine: use sendmsg/recvmsg instead of sendto/recvfrom
authorThiago Macieira <thiago.macieira@intel.com>
Tue, 10 Mar 2015 22:09:29 +0000 (15:09 -0700)
committerThiago Macieira <thiago.macieira@intel.com>
Sat, 22 Aug 2015 22:26:30 +0000 (22:26 +0000)
commitef05ad0ac500c10b1a3ae254d8a07968d6cf0c9e
treef2545760293240883c22bffe71d4fab48484dfc5
parent5b38454714fdbf8d4acffe482aaa32b91a4b5d98
QNativeSocketEngine: use sendmsg/recvmsg instead of sendto/recvfrom

We'll need to use these functions instead of the ones we're currently
using in order to access the ancillary data.

Note that on Windows the two functions aren't globals, but must be
obtained via ioctl, which means they can fail. If they do, we fall back
to using WSARecvFrom/WSASendTo

Change-Id: Iee8cbc07c4434ce9b560ffff13ca4284acd24132
Reviewed-by: Richard J. Moore <rich@kde.org>
src/network/socket/qnativesocketengine_p.h
src/network/socket/qnativesocketengine_unix.cpp
src/network/socket/qnativesocketengine_win.cpp
src/network/socket/qnet_unix_p.h