summaryrefslogtreecommitdiffstats
path: root/src/network/access/qnetworkaccessbackend.cpp
diff options
context:
space:
mode:
authorPeter Hartmann <peter.hartmann@nokia.com>2010-11-17 17:33:22 (GMT)
committerPeter Hartmann <peter.hartmann@nokia.com>2010-11-23 14:54:33 (GMT)
commitad1e82323225e996720136e8b2d669166b8d8441 (patch)
tree754b92c1de65167a78cbe3dc183e009812f8af9f /src/network/access/qnetworkaccessbackend.cpp
parentb1c412cefa51f0eea79dbf279f2a23414ccecc3d (diff)
downloadQt-ad1e82323225e996720136e8b2d669166b8d8441.zip
Qt-ad1e82323225e996720136e8b2d669166b8d8441.tar.gz
Qt-ad1e82323225e996720136e8b2d669166b8d8441.tar.bz2
QNetworkAccessManager: enable synchronous HTTP calls
To enable synchronous calls, an attribute in the QNetworkRequest has to be set. If set, when QNetworkAccessManager::get() (and post(), put()) returns, the reply is finished and all data has been read in case of success. This feature is semi-public for now (usable, but not documented). To enable this, an attribute in the QNetworkRequest must be set. If this attribute is set, we open a new connection to the server with only one channel and call the channels' sockets' waitFor* methods. Reviewed-by: Markus Goetz
Diffstat (limited to 'src/network/access/qnetworkaccessbackend.cpp')
-rw-r--r--src/network/access/qnetworkaccessbackend.cpp1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/network/access/qnetworkaccessbackend.cpp b/src/network/access/qnetworkaccessbackend.cpp
index 05eb6cb..12b6400 100644
--- a/src/network/access/qnetworkaccessbackend.cpp
+++ b/src/network/access/qnetworkaccessbackend.cpp
@@ -142,6 +142,7 @@ void QNetworkAccessBackend::emitReplyUploadProgress(qint64 bytesSent, qint64 byt
QNetworkAccessBackend::QNetworkAccessBackend()
: manager(0)
, reply(0)
+ , synchronous(false)
{
}