f9c07da7b6
It's the right thing to do, as we're in 2017, not 1997. Also, this takes care to indicate that QAbstractSocket::MulticastTtlOption makes sense mostly for IPv4, even though it's implemented for both families. In IPv4, it's used to indicatae the scope, whereas in IPv6 it's stored in bits 12-15 of the address. Task-number: QTBUG-46046 Change-Id: I9741f017961b410c910dfffd14ffaabe0a2024d8 Reviewed-by: Mårten Nordheim <marten.nordheim@qt.io> Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io> |
||
---|---|---|
.. | ||
bearermonitor | ||
blockingfortuneclient | ||
broadcastreceiver | ||
broadcastsender | ||
dnslookup | ||
doc | ||
download | ||
downloadmanager | ||
fortuneclient | ||
fortuneserver | ||
googlesuggest | ||
http | ||
loopback | ||
multicastreceiver | ||
multicastsender | ||
multistreamclient | ||
multistreamserver | ||
network-chat | ||
securesocketclient | ||
shared | ||
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.