[Bug 28197] Account.I.External: support for immutable accounts in Mission Control

[bugzilla-daemon at freedesktop.org]

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

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

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

--- Comment #12 from Simon McVittie <simon.mcvittie at collabora.co.uk> 2010-06-18 08:26:51 PDT ---
Thanks, please merge the revised version as a draft.

Things I'm unsure about, which I'd like to sort out before undrafting (possibly
by someone overruling me):

"Cannot_Set_Enabledness" seems a bit awkward: do the rest of the spec cabal
prefer that, or the "Cannot_Set_Enabled" that I suggested?

Given that the interpretation of StorageSpecificInformation is
backend-specific, why would clients prefer to use it rather than going directly
to the backend? The only benefit I can think of is if you know that two
backends agree on the meaning of some keys, which seems fairly tenuous.

The lack of change-notification make StorageSpecificInformation somewhat
useless for round-trip avoidance, unless you happen to know that the keys
you're interested in are immutable.

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