[Telepathy] Display names from SIP headers as aliases?
Simon McVittie
simon.mcvittie at collabora.co.uk
Fri May 11 06:11:21 PDT 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 11 May 2007 at 15:30:31 +0300, mikhail.zabaluev at nokia.com wrote:
> There has been a discussion about improving the Aliasing interface.
> I have a tangent interest here, in that I consider using the interface to expose display names for contacts
That's the intention, yes - we expect clients to use Aliasing where
possible.
> as sent and received with SIP protocol messages. Just as in RFC2822 messages, SIP addressing headers From: and To: may include a human-friendly name along with the address URI.
Is this commonly done by other SIP clients, and do other SIP clients
usually fill it in with something useful? If so, then this sounds like a
nice feature.
> If the Aliasing interface is used for that, it may necessitate caching display names along with contact handles for the lifetime of a Connection. That's the only implementation concern I have with the current API.
The display name should be cached as qdata on the contact handle -
that's what we do in Gabble. This means if the contact handle loses all
its references (so clients are no longer able to query its alias), then the
display name is freed too.
Simon
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: OpenPGP key: http://www.pseudorandom.co.uk/2003/contact/ or pgp.net
iD8DBQFGRGt5WSc8zVUw7HYRAjgrAJ9ZQF2nb/4YBC9FKHwOIp/deDk5bQCfQ0f+
QKpZLgWnZH9RW8UYSTrmZQ0=
=kPZO
-----END PGP SIGNATURE-----
More information about the Telepathy
mailing list