A QML engine uses
QNetworkAccessManagerfor all network access. By implementing a factory, it is possible to provide the QML engine with custom
QNetworkAccessManagerinstances with specialized caching, proxy and cookies support.
Note the QML engine may create
QNetworkAccessManagerinstances from multiple threads. Because of this, the implementation of the
create()method must be
reentrant. In addition, the developer should be careful if the signals of the object to be returned from
create()are connected to the slots of an object that may be created in a different thread:
The QML engine internally handles all requests, and cleans up any
QNetworkReplyobjects it creates. Receiving the
finished()signal in another thread may not provide the receiver with a valid reply object if it has already been deleted.
Authentication details provided to
authenticationRequired()must be provided immediately, so this signal cannot be connected as a
QueuedConnection(or as the default
AutoConnectionfrom another thread).
For more information about signals and threads, see Threads and QObjects and Signals and Slots Across Threads.
Network Access Manager Factory Example
- Return type
Creates and returns a network access manager with the specified
parent. This method must return a new
QNetworkAccessManagerinstance each time it is called.
Note: this method may be called by multiple threads, so ensure the implementation of this method is reentrant.
© 2020 The Qt Company Ltd. Documentation contributions included herein are the copyrights of their respective owners. The documentation provided herein is licensed under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation. Qt and respective logos are trademarks of The Qt Company Ltd. in Finland and/or other countries worldwide. All other trademarks are property of their respective owners.