I think that the iq packet MUST be handled atomically. So either all changes are made or none are. (you'll probably struggle to find a server that implements this though)
On 11/23/05, Vinod Panicker <[EMAIL PROTECTED]> wrote: > On 11/23/05, Alexey Nezhdanov <[EMAIL PROTECTED]> wrote: > > В сообщении от Среда 23 Ноябрь 2005 14:59 Vinod Panicker написал(a): > > > On 11/23/05, Ralph Meijer <[EMAIL PROTECTED]> wrote: > > > > > PS: Any thoughts on the multiple iq items error handling anyone? > > > > > > > > What do you mean? An iq may only have 1 child element. > > > > > > Considering this stanza - > > > > > > Sorry! The stanza should have been like this - > > > > > > <iq from='[EMAIL PROTECTED]/balcony' type='set' id='roster_4'> > > > <query xmlns='jabber:iq:roster'> > > > <item jid='[EMAIL PROTECTED]' subscription='remove'/> > > > <item jid='[EMAIL PROTECTED]' subscription='remove'/> > > > <item jid='[EMAIL PROTECTED]' subscription='remove'/> > > > </query> > > > </iq> > > > > > > What if there are errors for any of the items? > > Why not do it like this? > > <iq from='[EMAIL PROTECTED]/balcony' type='set' id='roster_4'> > > <query xmlns='jabber:iq:roster'> > > <item jid='[EMAIL PROTECTED]' subscription='remove'/> > > </query> > > </iq> > > <iq from='[EMAIL PROTECTED]/balcony' type='set' id='roster_5'> > > <query xmlns='jabber:iq:roster'> > > <item jid='[EMAIL PROTECTED]' subscription='remove'/> > > </query> > > </iq> > > <iq from='[EMAIL PROTECTED]/balcony' type='set' id='roster_6'> > > <query xmlns='jabber:iq:roster'> > > <item jid='[EMAIL PROTECTED]' subscription='remove'/> > > </query> > > </iq> > > Anyways user will very rarely delete several contacts at once... What is the > > benefit from doing it in your way? > > I figured since its not expressly forbidden, then why not? > > Maybe bulk automated operations? Who knows? > > Regards, > Vinod. > -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/
