[Bug 32023] add a way to make a TpContact synchronously, if the CM is modern

[bugzilla-daemon at freedesktop.org]

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

Guillaume Desmottes <guillaume.desmottes at collabora.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
  Status Whiteboard|                            |r+

--- Comment #1 from Guillaume Desmottes <guillaume.desmottes at collabora.co.uk> 2010-12-02 01:47:51 PST ---
Branch looks good but I have a few questions.

I guess we'll make immortable handles mandatory in TP 1.0. Then this function
could be renamed tp_connection_dup_contact_for_handle(), adds a note somewhere
to not forget?

(In reply to comment #0)
> * if the connection has immortal handles and we know the handle and we know the
> identifier, make a TpContact synchronously (needs new API, see branch) and
> signal the event straight away

How can a client easily check if a handle is known?

> * else if we have a cached TpContact (needs new API, not yet written) signal
> the event straight away

I guess TpTextChannel should use this one as all it gets is the sender handle
from the CM, right ?

> * else make a TpContact asynchronously and signal the event later; if you don't
> like your messages being re-ordered, upgrade your CM('s library)
> 
> Probably blocks Bug #27175, certainly blocks Bug #29531.

Should we make immortal handles a requierement for TpTextChannel? Factories
could create a TpTextChannel only if the connection implements immortal handles
but that assumes that the TpConnection passed to
tp_client_channel_factory_create_channel() as CORE ready so we can check.

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