summaryrefslogtreecommitdiffstats
path: root/translations/README
diff options
context:
space:
mode:
authorThiago Macieira <thiago.macieira@nokia.com>2009-04-03 14:51:21 (GMT)
committerThiago Macieira <thiago.macieira@nokia.com>2009-04-06 07:55:17 (GMT)
commitb11659ba9ea4532583398f6e539e78ed79a0c600 (patch)
tree20d6a95a1f626aaa3cc144140f39cbdf160d283b /translations/README
parent020ced4994bace0ed7f494bec8905afa959f76ed (diff)
downloadQt-b11659ba9ea4532583398f6e539e78ed79a0c600.zip
Qt-b11659ba9ea4532583398f6e539e78ed79a0c600.tar.gz
Qt-b11659ba9ea4532583398f6e539e78ed79a0c600.tar.bz2
Fix QNetworkReply's automatic pushing of a cache when the cache is
more than 64k. This issue was found by Warwick: the copyReadyRead() slot is called only once as a result of readyRead(), but since there's no more data to be received (the source QIODevice is a QBuffer), we'll never get a readyRead() again. So, if we don't have a limited buffer size, we should read everything. This applies to QFile as well. The side-effect is that we cause the entire QFile to be loaded to memory, so if you had a 2 GB cache entry, you'll probably run out of memory. Future optimisations: - don't memcpy the data from a QBuffer into another buffer - find a way to avoid loading the entire contents of the file (probably not possible with the default QNetworkDiskCache since that may compress the data, so we won't know the size and thus can't fake finished()) Reviewed-by: Warwick Allison
Diffstat (limited to 'translations/README')
0 files changed, 0 insertions, 0 deletions