summaryrefslogtreecommitdiffstats
path: root/src/network/access/qnetworkreplyhttpimpl_p.h
diff options
context:
space:
mode:
authorMarkus Goetz <markus@woboq.com>2014-09-19 17:18:59 +0200
committerMarkus Goetz <markus@woboq.com>2014-09-25 17:10:54 +0200
commit097b641c3eb588f1707f87e6a9bedb1d3d8cc31d (patch)
tree4e3fd9d417033e1a742cd2cc03dbd5a4fd214ba2 /src/network/access/qnetworkreplyhttpimpl_p.h
parent5c2d7b1635904da257938af740af024928b8ce5e (diff)
QNAM: Fix previous HTTP upload CPU fix
My previous fix for CPU load issues between HTTP thread and user thread was fragile if the upload QIODevice emitted readyRead() multiple times. [ChangeLog][QtNetwork][QNetworkAccessManager] Fix behavior of upload QIODevice that generate data on readyRead() for HTTP PUT/POST Change-Id: Idb1c2d5a382a704d8cc08fe03c55c883bfc95aa7 Reviewed-by: Christian Kamm <kamm@incasoftware.de> Reviewed-by: Richard J. Moore <rich@kde.org>
Diffstat (limited to 'src/network/access/qnetworkreplyhttpimpl_p.h')
-rw-r--r--src/network/access/qnetworkreplyhttpimpl_p.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/network/access/qnetworkreplyhttpimpl_p.h b/src/network/access/qnetworkreplyhttpimpl_p.h
index 06a5383ae4..4a5b61a227 100644
--- a/src/network/access/qnetworkreplyhttpimpl_p.h
+++ b/src/network/access/qnetworkreplyhttpimpl_p.h
@@ -212,6 +212,7 @@ public:
// upload
QNonContiguousByteDevice* createUploadByteDevice();
QSharedPointer<QNonContiguousByteDevice> uploadByteDevice;
+ bool uploadDeviceChoking; // if we couldn't readPointer() any data at the moment
QIODevice *outgoingData;
QSharedPointer<QRingBuffer> outgoingDataBuffer;
void emitReplyUploadProgress(qint64 bytesSent, qint64 bytesTotal); // dup?