Description
QIODevice has several shortcomings:
- it requires inheritance
- it buffers/copies data
- it is designed for synchronous usage
- error handling is limited
Separating the producing and consuming of data independent from how the data is processed, would give us a lot more flexibility, allowing piping, implementing a device without inheritance, and not be tied to a synchronous API.
Attachments
Issue Links
- relates to
-
QTBUG-19044 Make QML network loading use the QNetworkAccessManager zero-copy features
- Open
-
QTBUG-19169 Qt 5: readAny() API for zero-copy in QIODevice
- Open
-
QTBUG-6705 Bring "zero-copy" to QIODevice::read
- Closed