touch-packages team mailing list archive

[Michi Henning <michi.henning@xxxxxxxxxxxxx>]

The tri-state accessibility comes straight from QNetworkAccessManager:
http://doc.qt.io/qt-5/qnetworkaccessmanager.html#NetworkAccessibility-
enum

There is a discussion thread here: http://www.qtcentre.org/threads/37514
-use-of-QNetworkAccessManager-networkAccessible

I agree that the tri-state enum is useless. But the shell can't
magically fix it, I suspect. The best option is probably to just assume
that "Unknown" means the the same thing as "Not accessible". If bad
things happen that way, so be it: inside the scope is the wrong place to
fix this. It needs to be fixed in QNetworkAccessManager. (Failing that,
maybe in the shell, but that still smells bad.)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity-scopes-api in
Ubuntu.
https://bugs.launchpad.net/bugs/1502282

Title:
  "unknown" connectivity status problematic

Status in The Savilerow project:
  New
Status in unity-scopes-api package in Ubuntu:
  New

Bug description:
  metadata provides a scope a network connectivity status enum with three possible states:
  * connected
  * disconnected
  * unknown

  Sometimes unknown is the current state. This is quite problematic
  because in general a scopes that queries the network (that is, most
  scopes) need to know whether there is network or is not network and
  depending on this either make the network queries or display an error
  message.

  A status of unknown connectivity leaves the scope with no valid option:
  * the scope could assume the network is down and provide the user an error message. But often the network is not actually down, so this interrupts the user's flow unnecessarily
  *  the scope could assume the network is up, but this is dangerous if it is not up

To manage notifications about this bug go to:
https://bugs.launchpad.net/savilerow/+bug/1502282/+subscriptions