[Bug 24909] Anonymity API (e.g. suppressing caller-ID)

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=24909





--- Comment #16 from Will Thompson <will.thompson at collabora.co.uk>  2010-03-24 08:05:51 PST ---
So the Connection interface is used for setting the default, and then the
Channel.I.Anonymity.InitialAnonymityModes property can be included in requests
to override the default? I think each interface should explain its relationship
to the other.

Can the anonymity mode change mid-call? Should there be another property on the
channel for the flags that are *actually* in use (if you haven't set Mandatory:
True, that is)?

Speaking of which:

> Mandatory (16)
> This specifies that anonymity settings MUST be respected by the CM and any intermediaries between the local and remote contacts. If the anonymity settings cannot be followed, then the session MUST be denied with a org.freedesktop.Telepathy.Errors.NotAvailable error.

Maybe this should be a separate property. It seems a bit strange to have a
flagset where all the flags are features to hide except for one oddball flag
nestling in the middle. I think there should also be a separate error for "this
failed because your anonymity requirements weren't met".

telepathy-ring has a couple of connection properties which are also connection
parameters, using the DBus_Property parameter flag
(http://telepathy.freedesktop.org/spec/org.freedesktop.Telepathy.ConnectionManager.html#org.freedesktop.Telepathy.ConnectionManager.Conn_Mgr_Param_Flags).
If Conn.I.Anonymity had a read-write property rather than a read-only property
and a setter method, it could do the same.


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