On Wed, 22 Mar 2006 19:59:14 +0100
Jakob Schroeter <js@xxxxxxxxxx> wrote:
> Well, roster() is not the best place to do that. The roster really is
> some kind of static structure which does not contain any info about
> connected resources. The server just sends your contact's JIDs and at
> that time the ResourceMap is bound to be empty. Presence info, such
> as resources, is only added when presence stanzas come in from the
> individual contact's ssrvers. And since people can go offline and
> online at any time there is no point in creating such a list at
> startup. ;) Btw, the Roster already is such a map, you could simply
> re-use it.
Actually, i thought about creating a contact map to keep tracks of the
corresponding widget so a change would be applied to every group the
widget appears in (i never said i was a design pro :-).
Moreover, in my (somewhat limited) understanding, a contact list
consists of on/offline contacts (shown or not) so it felt natural to
"initialize" it with a "static" list (kinda leaving resources on the
side).
Anyway, thanks for the clarification, can't get everything right the
first time. ;-)
Cheers,
Vincent
--
gloox-dev mailing list
to unsubscribe:
send a message with subject 'unsubscribe gloox-dev' to minimalist@xxxxxxxxxx