Well, to partially answer my own questions, I worked my way around this by
using the deprecated trackID and setting up a IQ Handler to manage it.
Should I have been called back in handleUnsubscriptionResult?
thanks,
jon
On Fri, Oct 16, 2009 at 1:33 AM, Jon Steer <jsteer@xxxxxxxxxxxx> wrote:
> What callback should I expect upon receiving the result of this
> unsubscribe? I was expecting "handleUnsubscriptionResult" but it doesn't
> get called?
>
> <iq to='pubsub.mydomain.com' id='uid4' type='set' from='
> jsteer@xxxxxxxxxxxx/myresource' xmlns='jabber:client'>
> <pubsub xmlns='http://jabber.org/protocol/pubsub'>
> <unsubscribe node='mynode' jid='jsteer@xxxxxxxxxxxx'
> subid='5L2wWhaNyJW803cj92H78oDW9x5q4Xodh7kB3WKz'/>
> </pubsub>
> </iq>
>
> <iq type='result' id='uid4' from='pubsub.mydomain.com' to='
> jsteer@xxxxxxxxxxxx/myresource'/<http://jsteer@xxxxxxxxxxxx/myresource%27/>
> >
>
>
> Thanks,
> jon
>
> --
> "Don't stand still, if you see me running down the road, 'cause there is
> trouble right behind me".
>
--
"Don't stand still, if you see me running down the road, 'cause there is
trouble right behind me".