diff options
Diffstat (limited to 'src/network/kernel/qnetworkdatagram.cpp')
-rw-r--r-- | src/network/kernel/qnetworkdatagram.cpp | 15 |
1 files changed, 2 insertions, 13 deletions
diff --git a/src/network/kernel/qnetworkdatagram.cpp b/src/network/kernel/qnetworkdatagram.cpp index 50421fa7f5..c8c87d4549 100644 --- a/src/network/kernel/qnetworkdatagram.cpp +++ b/src/network/kernel/qnetworkdatagram.cpp @@ -450,16 +450,7 @@ void QNetworkDatagram::setData(const QByteArray &data) way of responding to a datagram back to the original sender. Example: - \code - void Server::readPendingDatagrams() - { - while (udpSocket->hasPendingDatagrams()) { - QNetworkDatagram datagram = udpSocket->receiveDatagram(); - QByteArray replyData = processThePayload(datagram.data()); - udpSocket->writeDatagram(datagram.makeReply(replyData)); - } - } - \endcode + \snippet code/src_network_kernel_qnetworkdatagram.cpp 0 This function is especially convenient since it will automatically copy parameters from this datagram to the new datagram as appropriate: @@ -491,9 +482,7 @@ void QNetworkDatagram::setData(const QByteArray &data) overloads, so it is a good idea to make sure this object is rvalue, if possible, before calling makeReply, so as to make better use of move semantics. To achieve that, the example above would use: - \code - udpSocket->writeDatagram(std::move(datagram).makeReply(replyData)); - \endcode + \snippet code/src_network_kernel_qnetworkdatagram.cpp 1 */ |