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) locally.
2013/3/15 Xavier Claessens <xclae...@gmail.com> > Le vendredi 15 mars 2013 à 09:29 +0100, Xavier Claessens a écrit : > > 2) Avatar cache: offline XMPP contacts does not know their avatar token, > > but we should still announce the last known avatar. > > > > -> IMHO it makes no sense to write avatars on disk in multiple places, > > so we should reuse the existing avatar cache. So gabble could store on > > disk a contact-id -> avatar-cache-uri map. With the new spec that's > > enough because we expose only the URI to clients. > > (...) > > > Suggestions > > ----------- > > > > - I think 1, 2 and 3 are all already pretty well covered, just need to > > land TpAvatarsMixin work. > > Actually 2 is not covered, the contact-id -> avatar-cache-uri map can be > shared with the offline cache exposed in my point 7. So we would have > all contact attributes serialized into a file, we can easily extract the > avatar URI from that. > > Regards, > Xavier Claessens. > > _______________________________________________ > telepathy mailing list > telepathy@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/telepathy >
_______________________________________________ telepathy mailing list telepathy@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/telepathy
