[Bug 26866] add support for requesting handles for a vCard field or URI

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Aug 17 19:03:45 CEST 2010


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

--- Comment #9 from Eitan Isaacson <eitan.isaacson at collabora.co.uk> 2010-08-17 10:03:45 PDT ---
These are all the additions I got so far. 

Protocol.AddressableVCardFields: as
Used when offline to determine the what vCard fields we could use to request
handles/channels.

Connection.RequestHandlesByVCardField(s: Field, as: Values) → au: Handles
Used for getting a handle with a vCard field.

Channel.TargetVCardField: s
Channel.TargetVCardAddress: s
Immutable properties.

Conn.I.Requests.RequestableChannelClasses
TargetVCardField could appear as a fixed property (with a value, like "TEL"),
and TargetVCardAddress could appear as an allowed property. This is for
determining capabilities when online. It also affects
Connection.RequestHandlesByVCardField which is kind of weird, but not
completely irrational.

(In reply to comment #8)
> So, if we add something like:
> 
>   Protocol.AddressableVCardFields: as
>   Connection.RequestHandlesByVCardField(s: Field, as: Values) → au: Handles
>   Channel.TargetVCardField: s
> 
> Then for connections that are offline you can look at the Protocol to determine
> what types of contact they support addressing; for those that are online, you
> can either still use that, or for a better idea look in
> RequestableChannelClasses. I think this means we don't need an equivalent of
> AddressableVCardFields on the Connection (for cases like XMPP where, in
> general, we only support X-JABBER, but when we connect it might turn out that
> our server has a SIP or POTS gateway).
> 
> So we want some way to store what we have discovered. But we also need a way
> for the user to configure it, as mentioned in bug 24898. I'll take some
> thoughts on that over there.

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


More information about the telepathy-bugs mailing list