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

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Jun 18 19:41:56 CEST 2010


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

--- Comment #13 from Eitan Isaacson <eitan.isaacson at collabora.co.uk> 2010-06-18 10:41:56 PDT ---
(In reply to comment #12)
> 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?
> 

I agree, I'll change it.

> 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.
> 

There is that, and also the fact that you don't need any hard dependencies in
the UI, just an awareness of the other stores out there. It makes what I am
doing now much easier.

> 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.

Maybe this should be immutable as well.

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



More information about the telepathy-bugs mailing list