[Bug 28192] support for immutable accounts in Mission Control

[bugzilla-daemon at freedesktop.org]

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

--- Comment #2 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-05-21 03:14:28 PDT ---
(In reply to comment #1)
> This branch does not use the External property to enforce any policy, i.e.
> calling 'Set' does not prevent the property from being set. This is currently
> left up to the plugins to handle.

See also the "always-on" property on McdAccount, which has the following
semantics if TRUE:

* cannot be disabled
* ConnectAutomatically cannot be false
* RequestedPresence cannot be offline

(This is exactly what you want for the singleton cellular account on an N900,
which is brought into existence by osso-mission-control.)

In practice, I don't think External's effects are going to be the same for all
accounts it's applied to:

* a Facebook Chat (XMPP) or other social-network-attached account can still be
put online/offline and probably even disabled (the UI widget would ideally be
labelled "disable Facebook Chat" to indicate that it only affects MC); it
doesn't make sense to change its 'account' or 'password' parameters, but other
Parameters (proxy server?) are likely to make sense to change

* a cellular account probably can't be taken offline or disabled, but its
Parameters (e.g. SMS centre and SMS validity time on N900) can be altered
freely

Perhaps we want a read-only A.I.External.AlwaysOn property to indicate the
"always-on" semantics?

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