[Bug 24896] Account.Interface.Conditions

[bugzilla-daemon at freedesktop.org]

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

Simon McVittie <simon.mcvittie at collabora.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Status Whiteboard|                            |review+ as draft

--- Comment #8 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-09-29 08:38:59 PDT ---
I think this is ready to be a draft. Is anyone working on an implementation?

> +      <p>In cases where it would be beneficial for the user to (temporarily)
> +        override connectivity conditions the user should disable connectivity
> +        checking by means outside of scope of this specification.</p>
...
> +          managed by NM, the user could turn off the checks by configuring the
>            account manager or its connectivity plugins.</p>

This is a bit of a cop-out: Account and AccountManager *are* how you configure
the account manager :-)

It seems reasonable to leave this for later definition, but I think having at
least some idea how this works is an undraft blocker. It could be as simple as
having a method Account.Interface.Connectivity.TryAnyway() you can use to try
an unconnected account "just this once".

> +        <li>vpn - s: VPN ID, or absent if not connected to a VPN</li>

Just thought of: what if you're connected to more than one VPN? You might
reasonably have an OpenVPN link to your home server and another to your office,
for instance?

One possibility would be to set { vpn-openvpn.example.net: True,
vpn-vpn.collabora.co.uk: True } or something.

Being connected to more than one WLAN is possible (I think NM might even
support it?) but somewhat pathological, so I think we can define 'essid' to be
whichever WLAN ESSID your default route goes through. Similar for 'cellular'.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.