GNOME Bugzilla – Bug 643718
Add support for refreshing poll-based backends
Last modified: 2018-08-04 08:25:29 UTC
The services Folks has dealt with so far (well, IM…) generally has information pushed to the user by the service. This will change with the advent of the libsocialweb backend (bug 638280), for instance.
There are broadly two options for coping with these services:
• have API for the application using Folks to explicitly request an update for a particular set of contacts;
• poll every so often.
I guess the second can be implemented in terms of the first. :)
Which strategy is appropriate depends on the nature of the information being shown. For instance, a contact's birthday is unlikely to change frequently, so very sporadic polling (of the order of days/weeks) is enough to keep this reasonably up-to-date. At the other end of the spectrum, out-of-date status message or geolocation information is very noticeable to the user, so it would be preferable to poll reasonably frequently while the user is watching, and never when the user is not.
Relatedly, having smarter querying API in libfolks (rather than “here's a big set of individuals; search it”) would allow it to make more targeted requests to the server to explicitly refresh information, rather than having one big refresh() button.
(I note that contact information updates on Jabber are not pushed to the user, and Telepathy has API for explicitly requesting updates in this case: <http://telepathy.freedesktop.org/spec/Connection_Interface_Contact_Info.html#Method:RefreshContactInfo>. This is expensive in terms of bandwidth on XMPP: the contact information on the wire includes a base64-encoded copy of the contact's avatar …)
From the discussion at the hackfest today:
• Provide a “refresh me now” method on PersonaStores.
• libfolks *will* set up a timeout for refreshing PersonaStores automatically. We need to determine a reasonable default value for this timeout, taking API key conditions (e.g. maximum of 50000 queries per day) into account.
Punting bugs that won't be fixed by Folks 0.6.0.
-- GitLab Migration Automatic Message --
This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.
You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/folks/issues/11.