[Bug 45853] telepathy-gabble does not persist OLPC pubsub data

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=45853

--- Comment #5 from Guillaume Desmottes <guillaume.desmottes at collabora.co.uk> 2012-02-15 00:37:19 PST ---
(In reply to comment #4)
> telepathy connects to the server and the server sends the last published items of the PEP nodes of the user. telepathy broadcasts this info as signals but then
> forgets the information (doesn't cache it). Right?

Yes, this code is very old (5 years ago) and at this time ejabbard wasn't supporting last item sending when connecting. Ideally Gabble should cache this (as it
does with location for example) so it wouldn't have to make a query each time.

> Sugar then tries to enumerate each buddy on the connection as follows:
>    self.connection[CONNECTION_INTERFACE_BUDDY_INFO].GetProperties(handle)
> 
> which causes an <iq type=get> request to be sent to the server, but in this case the jabber server returns an empty result, and I think this is correct.

It's not. The server should return the last value published by the user.

> specs seem to say that the jabber server has to cache or store the last item published, and send it to new clients as they connect (as you note above) due to
> on_sub_and_presence, but it doesn't say that the server has to then keep that info around for later and resend it on-demand.

Well, how is it supposed to send the last data published by each user when connecting if it does store it? :)
last-item is really just there to avoid manually requesting the node for each of your contact. But we use to work fine without it.

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