[Bug 41148] NM: better handling of connectivity changes

[bugzilla-daemon at freedesktop.org]

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

--- Comment #4 from Simon McVittie <simon.mcvittie at collabora.co.uk> ---
I'm inclined to agree with Will: I think CMs should take responsibility for
detecting when they've lost their network connections, because only the CM
knows how much connectivity it actually needs, and more importantly, which
local IP address it's actually using. Having MC try to guess is error-prone,
and having the CM tell MC what's going on would need a significant amount of
D-Bus API.

I'd be tempted to add something like this:

    property Protocol.ConnectivityFlags: immutable readable Connectivity_Flags

    flags Connectivity_Flags:
        # This CM does not need an Internet connection.
        # (telepathy-ring, telepathy-salut)
        INTERNET_NOT_REQUIRED,

        # Connections for CM will automatically disconnect itself if
        # required. MC shouldn't second-guess it.
        MANAGES_OWN_DISCONNECTION,

and that'd give us 95% of the Conditions interface (Bug #24896) straight away.
The rest is speculative generality about "what if I have a SIP account that
should only be connected when I'm at the office, or when I'm on a particular
VPN?" which, to be honest, could be implemented by manipulating the Enabled
flag.

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