summaryrefslogtreecommitdiffstats
path: root/src/network/access/qfilenetworkreply_p.h
Commit message (Collapse)AuthorAgeFilesLines
* QNAM: Rename QFileNetworkReply to QNetworkReplyFileImplMarkus Goetz2010-10-051-100/+0
| | | | | | | | 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
* QNAM: New QNetworkReply::setFinished() protected functionMarkus Goetz2010-08-241-2/+0
| | | | | | | | 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
* QFileNetworkReply: Use a QFileEngineMarkus Goetz2010-01-251-2/+5
| | | | | | Slight performance increase. Reviewed-by: Peter Hartmann
* Enhance QFileNetworkReplyMarkus Goetz2010-01-181-9/+1
| | | | | | | | 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
* Update copyright year to 2010Jason McDonald2010-01-061-1/+1
| | | | Reviewed-by: Trust Me
* Introduce QFileNetworkReply in QNetworkAccessManagerMarkus Goetz2009-11-131-0/+107
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