Shane Kearns a590e77fd8 Fix QNetworkConfigurationManager usage outside main thread first ... QNetworkConfigurationManager creates the engines loaded from plugins as objects in the main thread. If a QNetworkConfigurationManager instance is created in a worker thread without any instance previously existing in the main thread, then it is uninitialised until the main thread has run. This causes allConfigurations() to return an empty list if called immediately after instantiation, for example. This fix initialises the plugins using blocking queued connections, which causes the worker thread to block until the initialisation function has been called in the context of the main thread. Deadlock is possible if the main thread is for some reason waiting on the worker thread, but it will not deadlock on QNetworkConfigurationManager's mutex. If this is a problem for an application, it should use QNetworkConfigurationManager from the main thread first to preload the plugins. Task-number: QTBUG-18795 Task-number: QTBUG-18799 Reviewed-by: Cristiano Di Flora		2011-05-09 13:50:02 +02:00
..
.gitignore	Initial import from the monolithic Qt.	2011-04-27 12:05:43 +02:00
qnetworkproxyfactory.pro	Add autotests for configuration dependent network proxies	2011-05-09 13:15:47 +02:00
tst_qnetworkproxyfactory.cpp	Fix QNetworkConfigurationManager usage outside main thread first	2011-05-09 13:50:02 +02:00