c82d40749d
On OS X and Windows, this was not working, because the socket was being bound in v6 mode (due to ::Any being for dual mode), but the address passed was a v4 address, meaning it took the wrong codepath. Linux, strangely, apparently works anyway. This is fixable in OS X (by using the v6 join path when bound in v6/dual mode), but the same fix doesn't work on Windows, failing with WSAEADDRNOTAVAIL. Don't allow this behaviour, and provide a sane error message telling the user what to do instead. Done-with: Shane Kearns Task-number: QTBUG-25047 Change-Id: Iaf5bbee82e13ac92e11b60c558f5af9ce26f474b Reviewed-by: Shane Kearns <shane.kearns@accenture.com> |
||
---|---|---|
.. | ||
bearercloud | ||
bearermonitor | ||
blockingfortuneclient | ||
broadcastreceiver | ||
broadcastsender | ||
dnslookup | ||
download | ||
downloadmanager | ||
fortuneclient | ||
fortuneserver | ||
googlesuggest | ||
http | ||
loopback | ||
multicastreceiver | ||
multicastsender | ||
network-chat | ||
securesocketclient | ||
threadedfortuneserver | ||
torrent | ||
network.pro | ||
README |
Qt is provided with an extensive set of network classes to support both client-based and server side network programming. These examples demonstrate the fundamental aspects of network programming with Qt. Documentation for these examples can be found via the Examples link in the main Qt documentation.