[Gossip-dev] Questions about GossipContactManager

[Xavier Claessens]

Hello,

I'm fixing telepathy backend to use the new API and contact manager.
Here are my problems:

1) Is gossip_protocol_find_contact() still useful ? Shouldn't we use
gossip_contact_manager_find() instead now ?

2) When gossip starts, gossip_protocol_new_contact() is called to create
all contacts saved in a xml file. That's useful for offline viewing logs
and others reasons... But should the backend keep those contacts even if
it's not connected ? Backend can't request avatar/alias/etc before
connecting. When disonnecting GossipJabber protocol it removes all
contacts from its hash table but contact manager don't, so the sate is
not coerent between offline before first connection and offline after
first connection. What should be done here ?

3) Using telepathy we can't know own-contact's ID before connecting
account. GossipContactManager gets own contact from the protocol even if
offline, is it a problem if it returns a GossipContact with NULL ID and
create a new GossipContact object (Previous one is finalized) with all
information once the account is connected ?

4) If jabber backend the own contact is created in jabber_setup() and
its ID is set to the account's "account" param which is OK, but if we
change the jid of the account and then connect it jid of the account and
the one of own contact won't be equal I guess ? Potential problem here I
think.

5) The contact manager should connect to "notify::name" on each
GossipContact object and store the file when a name change I think.

Xavier.