[Bug 68712] connectivity code is far too complicated

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=68712

--- Comment #8 from Simon McVittie <simon.mcvittie at collabora.co.uk> ---
Created attachment 84857
  --> https://bugs.freedesktop.org/attachment.cgi?id=84857&action=edit
08/16] Remove the concept of binding accounts to transports

We only have one transport now, so there are two options: either the
account is a special one that "needs dispatch" and also bypasses the
transport check (in practice this means cellular accounts), or it is
connected via the Internet.

Binding accounts to transports never made a vast amount of sense. If we
have many parallel Internet connections (e.g. wired + wifi + cellular +
VPN), Mission Control can't know which one a Connection is relying on -
only the connection manager can know that - so we have to err on the
side of disconnecting everything on a connectivity change anyway.

A possible refinement in future Tp versions would be a way for a CM
to tell MC "this connection does its own connectivity-monitoring,
so don't kick it when we get disconnected". For now, we assume that
everything needs the Internet, unless it's one of the accounts that
wouldn't previously have been bound to a connection (i.e.
_mcd_account_needs_dispatch() returns FALSE).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.