Uploaded image for project: 'Qt'
  1. Qt
  2. QTBUG-136625

Integrate QNetworkInformation into QNetworkAccessManager to identify and react to connection issues (or document how to do it)

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • Icon: Not Evaluated Not Evaluated
    • None
    • None
    • Network
    • 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

      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.

        For Gerrit Dashboard: QTBUG-136625
        # Subject Branch Project Status CR V

            mate Máté Barany
            matthias_rauter Matthias Rauter
            Vladimir Minenko Vladimir Minenko
            Alex Blasche Alex Blasche
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: