From 8610226f6f43600a13186cf2ecb5d6bf3f45f4f1 Mon Sep 17 00:00:00 2001 From: Markus Goetz Date: Thu, 18 Jun 2009 17:40:21 +0200 Subject: QNetworkAccessManager: Clarify doc about deleting QNetworkReply Reviewed-by: Volker Hilsheimer (cherry picked from commit 8ef1e1fc0e4b741d2f85cc8c0df42858b9306ff8) --- src/network/access/qnetworkaccessmanager.cpp | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/src/network/access/qnetworkaccessmanager.cpp b/src/network/access/qnetworkaccessmanager.cpp index cbd0b53..676feb4 100644 --- a/src/network/access/qnetworkaccessmanager.cpp +++ b/src/network/access/qnetworkaccessmanager.cpp @@ -112,8 +112,6 @@ static void ensureInitialized() are supplied that take a request and optional data, and each return a QNetworkReply object. The returned object is used to obtain any data returned in response to the corresponding request. - the reply to is where most of the signals as well - as the downloaded data are posted. A simple download off the network could be accomplished with: \snippet doc/src/snippets/code/src_network_access_qnetworkaccessmanager.cpp 0 @@ -122,7 +120,8 @@ static void ensureInitialized() takes is the QNetworkReply object containing the downloaded data as well as meta-data (headers, etc.). - \note The slot is responsible for deleting the object at that point. + \note After the request has finished, it is the responsibility of the user + to delete the QNetworkReply object at an appropriate time. A more involved example, assuming the manager is already existent, can be: -- cgit v0.12