| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
This name is more intuitive since that class lives on the same
level as QNetworkReplyImpl and not on the lower level
like QHttpNetworkReply
Reviewed-by: Peter Hartmann
|
|
|
|
|
|
|
|
| |
This function custom allows subclasses of QNetworkReply to also
use the behaviour that is enabled by having isFinished().
Task-Number: QTBUG-11737
Reviewed-by: Peter Hartmann
|
|
|
|
|
|
| |
Slight performance increase.
Reviewed-by: Peter Hartmann
|
|
|
|
|
|
|
|
| |
It is now considered as finished immediatly after creation to avoid
an event loop spin.
Had to change the auto tests a bit to account for the new behaviour.
Reviewed-by: Peter Hartmann
|
|
|
|
| |
Reviewed-by: Trust Me
|
|
The QFileNetworkReply is a wrapper around QFile that
has therefore similar performance. This avoids
the usage of the unperformant QNetworkAccessFileBackend.
The benchmark qfile_vs_qnetworkaccessmanager shows
that the QFileNetworkReply's performance is better
than 0.9x of QFile compared to QNetworkAccessFileBackend
which had about 0.5x of QFile.
Reviewed-by: Peter Hartmann
|