On 12/7/05, Peter Saint-Andre <[EMAIL PROTECTED]> wrote: > Justin Karneges wrote: > > On Tuesday 06 December 2005 21:00, Peter Saint-Andre wrote: > >> OK, good. The spec is incomplete on this point mainly because we never > >> thought any client developer would generate something so "stupid". But > >> when you write these specs you often assume too much -- not everyone > >> comes to these specs with a background of Jabber development experience, > >> and what seems stupid to longtime Jabberites probably seems just fine to > >> a newbie. > > > > For mass operations it could make sense. What does jabberd do? What does > > JRU > > do? Might be worth investigating first. > > The jabber:iq:roster namespace was never meant for batch operations of > this kind -- not in 1999 when rosters were invented, not in 2002 when we > documented this stuff through the IETF, not in 2005 when someone > noticed a bug in the spec.
Apologies for reopening this thread after such a long time, but I found an instance where multiple item's are being sent in a single iq roster set. This is how Pandion renames a group in the client's roster - <iq type="set" id="sd72"> <query xmlns="jabber:iq:roster"> <item jid="[EMAIL PROTECTED]"> <group>NewGroup</group> </item> <item jid="[EMAIL PROTECTED]"> <group>NewGroup</group> </item> </query> </iq> Quite a valid scenario, I'd say... Regards, Vinod.