[jdev] IQ request response query

[Peter Saint-Andre]

Vinod Panicker wrote:
> On 11/11/05, Vinod Panicker <vinod.p at gmail.com> wrote:
>> Sorry!  The stanza should have been like this -
>>
>>   <iq from='juliet at example.com/balcony' type='set' id='roster_4'>
>>     <query xmlns='jabber:iq:roster'>
>>       <item jid='abc at example.com' subscription='remove'/>
>>       <item jid='def at example.com' subscription='remove'/>
>>       <item jid='ghi at example.com' subscription='remove'/>
>>     </query>
>>   </iq>
>>
>>
>> On 11/10/05, Jacek Konieczny <jajcus at jajcus.net> wrote:
>>> On Thu, Nov 10, 2005 at 04:00:47PM +0530, Vinod Panicker wrote:
>>>> Consider this scenario -
>>>>
>>>> Client sends IQ stanza for removing three roster items from the roster
>>>> of juliet at example.com .
>>>>
>>>>    <iq from='juliet at example.com/balcony' type='set' id='roster_4'>
>>>>      <query xmlns='jabber:iq:roster'>
>>>>        <item jid='abc at example.com' subscription='remove'/>
>>>>      </query>
>>>>      <query xmlns='jabber:iq:roster'>
>>>>        <item jid='def at example.com' subscription='remove'/>
>>>>      </query>
>>>>      <query xmlns='jabber:iq:roster'>
>>>>        <item jid='ghi at example.com' subscription='remove'/>
>>>>      </query>
>>>>    </iq>
>>> This is not a legal XMPP stanza. <iq/> stanza may contain only _one_
>>> payload element.
> 
> No closure on this, so what I'm doing is sending separate error and
> success stanzas to each of the items in the single iq stanza.

What do you mean, no closure? Please provide exactly what you are 
sending and receiving so we can critique it. Sending a separate roster 
push for each item removed seems appropriate if you are sending multiple 
removes in a single IQ set. However, sending multiple removes in a 
single IQ set seems wrong (or at least misguided) to me. I thought the 
spec prohibited including more than one <item/> when sending an IQ-set 
to the server, but I can't find that in RFC 3921. What is the use case 
for doing that? Perhaps we need to clean that up in rfc3921bis because I 
think it's a bad idea.

Peter

-- 
Peter Saint-Andre
Jabber Software Foundation
http://www.jabber.org/people/stpeter.shtml
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3641 bytes
Desc: S/MIME Cryptographic Signature
URL: <https://www.jabber.org/jdev/attachments/20051206/a04b7177/attachment-0002.bin>