2a80adc2f6
We don't key it on IP address anymore so we can drop the use of QMultiHash. This also requires moving the connections for error and disconnected to readyForUse so we don't remove an active connection when a second connection attempt happens from the same peer process. But since we still need to deallocate those connection attempts if they error out or simply disconnect, we connect their signals to the QObject::deleteLater slot. In some cases we might call deleteLater twice but that's fine. Change-Id: I48c27de1e51a52ef61cfb941a7a81b358ae9ce3f Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io> Reviewed-by: Konrad Kujawa <konrad.kujawa@qt.io> |
||
|---|---|---|
| .. | ||
| blockingfortuneclient | ||
| broadcastreceiver | ||
| broadcastsender | ||
| dnslookup | ||
| doc | ||
| fortuneclient | ||
| fortuneserver | ||
| http | ||
| multicastreceiver | ||
| multicastsender | ||
| multistreamclient | ||
| multistreamserver | ||
| network-chat | ||
| rsslisting | ||
| securesocketclient | ||
| secureudpclient | ||
| secureudpserver | ||
| shared | ||
| threadedfortuneserver | ||
| torrent | ||
| CMakeLists.txt | ||
| 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.