[JDEV] groups in groups

[Keith Minkler]

basically...

the current method was adopted, so that things like roster pushes could be implemented... things like roster changes,deletions, and additions can be dynamically pushed to the client, based on item.

basically, what it boils down to is, if you are thinking of the roster to be a bunch of groups with items in it, you are thinking about it the wrong way.. (even though the GUI suggests otherwise)... (hehe.. i never liked the display by group GUI anyway...)  

rosters contain items, and your roster should be a list of items keyed by jid, not group.. and each item contains the groups it is a member of.. it is also easier this way for an item to be in multiple groups, with out funky client logic to sort that all out.

also, in the future, roster items will contain much more than just <item/>s .. it will be a place to "bookmark" iq:browse locations, and store all sorts of interesting metadata.. (please note: if you think of jabber as just an instant messaging client/protocol you will not understand this paragraph).

that taken into account, it would be silly to group roster items inside of <group/> tags... it simply doesn't make sence.. 

Hope this answers all your questions...

Keith Minkler

On Wed, Sep 20, 2000 at 09:29:34PM -0700, Michael Abraham Shulman wrote:
> "Jens" == Jens Askengren <jensus at linux.nu> writes:
> 
> Jens> Do you mean that it would be impossible to have the same JID
> Jens> occur multiple times in a hierarchical roster reply? I don't
> Jens> think so.  It only requires the client to do a little smarter
> Jens> interpretation of the roster-reply than currently necessary.
> 
> Like this?
> 
> <group>
>   <item jid='me at somewhere'/>
> </group>
> <group>
>   <item jid='me at somewhere'/>
> </group>
> 
> I suppose that would work fine, and I don't know that the client would
> need to be all that much smarter.  I'm writing a client right now
> (will post details when it's usable) and it would certainly be easier
> to translate the roster info into a displayable form if it came in a
> hierarchical format.
> 
> Would someone (Keith?) care to enlighten us on why this format was
> rejected?  What turned out to be impractical about it?  I've glanced
> over the JDEV archives but I can't find any discussion on this
> subject.
> 
> \\// | R | T R | L B | //\\ ~ Michael Abraham Shulman
> mailto:shulman at caltech.edu  ~ jabber://mas@jabber.org
> http://kurukshetra.cjb.net/ ~ GnuPG Public Key #21A279E5
> 
> No poet or novelist wishes he was the only one who ever lived, but most of
> them wish they were the only one alive, and quite a number fondly believe
> their wish has been granted.
>         -- W.H. Auden, "The Dyer's Hand"
> 
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev