226d06402b
The system was just treating IP (and optionally port) as a unique identifier, so if a peer had multiple possible paths to a client they would connect multiple times. This fixes that by generating using QUuid in each client. We then use this during broadcast, replacing the username we sent before (which was not used), and as part of the greeting. The greeting now is more complex, since we need to send both username and the ID. Change-Id: I6c6c2ffd5198406aad48445a68dd6aab36de69c0 Reviewed-by: Konrad Kujawa <konrad.kujawa@qt.io> Reviewed-by: Timur Pocheptsov <timur.pocheptsov@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.