When I do:
<iq type='set'><query xmlns='jabber:iq:roster'><item
jid='[EMAIL PROTECTED]' name='julian-test'/></query></iq>
And then I send a presence subscribe request,
I get back:
<iq type='set'><query xmlns='jabber:iq:roster'><item
jid='[EMAIL PROTECTED]' name='julian-test' subscription='none'
ask='subscribe'/></query></iq>
Note the ask='subscribe'
Now, if I then do:
<iq type='set'><query xmlns='jabber:iq:roster'><item
jid='[EMAIL PROTECTED]'
name='julian-test'><group>testing</group></query></iq>
I get back:
<iq type='set'><query xmlns='jabber:iq:roster'><item
jid='[EMAIL PROTECTED]' name='julian-test'
subscription='none'><group>testing</group></query></iq>
No more ask='subscribe' ... It should not be the client's responsibility
to set the ask='subscribe', so the server is forgetting it. The client
needs ask='subscribe' to know if the user should be marked as
subscription pending, so this bug is a bit annoying.
Julian
--
email: [EMAIL PROTECTED]
jabber:[EMAIL PROTECTED]
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
