Le vendredi 15 mars 2013 à 10:06 -0500, Matthias Gehre a écrit : > When I read the telepathy spec > Connection.Interface.ContactList.ContactListPersists > > seemed to imply that the client would save the contact list if that > property > is set to false. But now I believe that no client actually looks at > that property.
Oh forgot about that property. The spec does not force any local storage format, like I described, but something like that would be needed in that case, yes. > > > 2013/3/15 Xavier Claessens <[email protected]> > > > > Le vendredi 15 mars 2013 à 08:50 -0500, Matthias Gehre a écrit : > > > I'm currently implementing a connection manager for WhatsApp, > which > > > does not allow > > > to request the roster at all. So we have to keep a copy of known > > > contacts (from adding them/receiving messages from them) > > > > This is the same situation than telepathy-sofiasip. Thanks for > bringing > > this, I did not cover that case. > > > > I'm wondering if the CM should implement the ContactList interfaces > > anyway, but keep the roster information locally in a file instead of > > relying on server storage. For this, it could use the offline > storage I > > describe in my point 6. So all API like adding/removing contacts, > > setting an alias, etc will just work like any other protocol. > > > > Regards, > > Xavier Claessens. > > > > > > _______________________________________________ > > telepathy mailing list > > [email protected] > > http://lists.freedesktop.org/mailman/listinfo/telepathy > > _______________________________________________ telepathy mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/telepathy
