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

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=12465





------- Comment #6 from mardy at users.sourceforge.net  2007-09-24 01:13 PST -------
(In reply to comment #5)
> The major problem we solve by using signals is that receiving a large avatar
> can take longer than the D-Bus method call timeout; once we've done the
> expensive part of the call (getting the avatar across the network), we might as
> well hand it over to the client (the cheap part of the call) even if it took so
> long that a method call would have timed out.

Well, the timeout can be raised up to several hours, that should be enough :-)

> Also, doing many method calls in parallel is problematic, because until very
> recent versions of D-Bus (which are not yet used on embedded platforms like the
> N800), there was a small maximum number of parallel pending calls allowed by
> the bus daemon (I think it was 32).

Yes, it is 32 in the N800. But I don't think that the specs should take that
into too much consideration; my suggestion is: don't deprecate the
RequestAvatar method, and add a RequestAvatars-like API that returns the
avatars in its return value.

And it wouldn't be too bad to add the avatar data in the Avatar(s)Updated
signal itself, since most listeners of this signal would also want to retrieve
the avatar, once they see that the token has changed. In this way the
RequestAvatars method calls would probably be more rare.


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