-
Suggestion
-
Resolution: Unresolved
-
Not Evaluated
-
None
-
None
-
25
-
8b82134ed (dev), 41625e544 (6.10), 17b8c5950 (dev), 4e2f3dbbd (6.10), 380ed8d48 (dev), 16c679727 (dev), fde5ceede (6.10), 8848e2078 (6.10)
-
Foundation Sprint 135, Foundation Sprint 136, Foundation Sprint 137, Foundation Sprint 138, Foundation Sprint 139, Foundation Sprint 140, Foundation Sprint 141
Removing QNetworkConnectionMonitor from QNetworkAccessManager QTBUG-136186 might leave us behind with a functional gap: We will not reliably recognize and react properly network connection drops.
There was the idea of replacing QNetConMon with QNetworkInformation within QNAM. This way we would take the burden of handling this away from our users.
While the idea is great (so was QNetConMon), there are arguments against it. Firstly, this is a functionality we never had everywhere, because QNetConMon never really took of on all platforms. Secondly, the complexity is high and might lead to more issues than it solves, leading to requests unexpectedly being aborted on due to QNetworkInfo.
- resulted from
-
QTBUG-136048 Analyse and resolve side effects resulting in drops of connectivity in Qt Quick apps when network connections change
-
- Closed
-
For Gerrit Dashboard: QTBUG-136625 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
681213,5 | Document Network Changes in QNetworkAccessManager | dev | qt/qtbase | Status: NEW | 0 | 0 |
682663,3 | Modify the http client to handle a network change | dev | qt/qtbase | Status: NEW | 0 | 0 |