This is one of a number of things that has been inconsistent
from one server to the next. First one server does the right
thing, then next server forgets to always include the ask
parameter. I've used the 1.0, 1.1, 1.2, 1.4 and now the 2.0
servers, so I cannot remember which does which.
I did report this bug in one of the servers a while back and
someone told me that they fixed it.
-Robert
> -----Original Message-----
> From: Julian Missig [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, May 20, 2001 3:40 PM
> To: [EMAIL PROTECTED]
> Subject: [JDEV] Possible bug with ask='subscribe'
>
>
> 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
>
_______________________________________________
jdev mailing list
[EMAIL PROTECTED]
http://mailman.jabber.org/listinfo/jdev
