[Telepathy] [Bug 12465] Current avatars API is likely to generate too much DBus traffic

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Jan 22 04:51:28 PST 2008


--- Comment #12 from Simon McVittie <simon.mcvittie at collabora.co.uk>  2008-01-22 04:51:28 PST ---
Mardy: we appear to be in violent agreement, and what you're talking about in
the last comment is fine. Gabble already holds avatars in RAM, and ptlo
recently fixed it to be able to reply to multiple requests with one
AvatarRetrieved signal.

For the record: in the current design, other CMs SHOULD cache (at least a few)
avatars during the lifetime of the Connection (to avoid repeated round trips to
the server), MUST NOT cache avatars beyond the lifetime of a Connection (CMs
shouldn't be stateful beyond a Connection's lifetime - that's an invariant of
our API), and SHOULD NOT rely on being able to save avatars to the filesystem
(they should cache them in RAM).

If you still believe the API is unworkable, bring it up with Rob, but please
implement it anyway. I don't think re-badgering the Avatars API takes priority
over everything else API-related that we're trying to work on (notably, MC).

[Capitalized words used in accordance with the RFC whose number I can never

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

More information about the Telepathy mailing list