Hi Jakob,
As stated in the Gloox 1.0 documentation:
virtual void handleRoster ( const Roster & roster ) [pure virtual]
Reimplement this function if you want to receive the whole server-side
roster on the initial roster push. After successful authentication,
RosterManager asks the server for the full server-side roster.
Invocation of this method announces its arrival. Roster item status is
set to 'unavailable' until incoming presence info updates it. A full
roster push only happens once per connection.
However, this function is not called only on initial connect but
whenever handleRosterPresence is called too. So the scenario goes like
this: handleRosterPresence announces the changes of a roster item and
then the handleRoster is called right after that. Version used: 1.0
from svn, code used: roseter example from the 1.0 svn.
Best,
Marcus
--
gloox-dev mailing list
to unsubscribe:
send a message with subject 'unsubscribe gloox-dev' to minimalist@xxxxxxxxxx