eb61d49ab3
Their use of QtNetwork is already covered by the HTTP example. While showcasing that QNAM easily deals with multiple simultaneous requests, waiting until finished() is emitted to write anything is not exactly idiomatic. And managing your own queue to only have one request running at a time is a weird example for an asynchronous framework. In this regard, having an example for a complete download manager (with a GUI) would be interesting, but may ultimately be very time-consuming to make for limited gain. Task-number: QTBUG-110643 Pick-to: 6.5 Change-Id: I6b2c1546b85fa89ab7ce1ff5565b0293b5710b74 Reviewed-by: Timur Pocheptsov <timur.pocheptsov@qt.io> Reviewed-by: Ievgenii Meshcheriakov <ievgenii.meshcheriakov@qt.io> Reviewed-by: Konrad Kujawa <konrad.kujawa@qt.io> |
||
---|---|---|
.. | ||
blockingfortuneclient | ||
broadcastreceiver | ||
broadcastsender | ||
dnslookup | ||
doc | ||
fortuneclient | ||
fortuneserver | ||
http | ||
loopback | ||
multicastreceiver | ||
multicastsender | ||
multistreamclient | ||
multistreamserver | ||
network-chat | ||
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.