summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMarkus Goetz <Markus.Goetz@nokia.com>2009-06-18 17:40:21 +0200
committerJason McDonald <jason.mcdonald@nokia.com>2009-06-20 14:46:16 +1000
commit8610226f6f43600a13186cf2ecb5d6bf3f45f4f1 (patch)
treedd95cd18867e8a25511950943b2d3dc76df0ffbb
parent6794d144c9427c852d776d426dcfd05c55ce372d (diff)
QNetworkAccessManager: Clarify doc about deleting QNetworkReply
Reviewed-by: Volker Hilsheimer (cherry picked from commit 8ef1e1fc0e4b741d2f85cc8c0df42858b9306ff8)
-rw-r--r--src/network/access/qnetworkaccessmanager.cpp5
1 files changed, 2 insertions, 3 deletions
diff --git a/src/network/access/qnetworkaccessmanager.cpp b/src/network/access/qnetworkaccessmanager.cpp
index cbd0b53a8b..676feb4416 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: