[ 
https://issues.apache.org/jira/browse/VYSPER-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Jakl closed VYSPER-52.
------------------------------

    Resolution: Fixed

Patch applied. VYSPER-65 deals with the error cases.

> Subscribe to a Node (XEP-0060 6.1)
> ----------------------------------
>
>                 Key: VYSPER-52
>                 URL: https://issues.apache.org/jira/browse/VYSPER-52
>             Project: VYSPER
>          Issue Type: Sub-task
>            Reporter: Michael Jakl
>            Assignee: Michael Jakl
>         Attachments: VYSPER-52.1.patch
>
>
> Example 30. Entity subscribes to a node
> <iq type='set'
>     from='[email protected]/barracks'
>     to='pubsub.shakespeare.lit'
>     id='sub1'>
>   <pubsub xmlns='http://jabber.org/protocol/pubsub'>
>     <subscribe
>         node='princely_musings'
>         jid='[email protected]'/>
>   </pubsub>
> </iq>
>       
> 6.1.2 Success Case
> If the subscription request is successfully processed, the server MUST inform 
> the requesting entity that it is now subscribed (which MAY include a 
> service-generated SubID).
> Example 31. Service replies with success
> <iq type='result'
>     from='pubsub.shakespeare.lit'
>     to='[email protected]/barracks'
>     id='sub1'>
>   <pubsub xmlns='http://jabber.org/protocol/pubsub'>
>     <subscription
>         node='princely_musings'
>         jid='[email protected]'
>         subid='ba49252aaa4f5d320c24d3766f0bdcade78c78d3'
>         subscription='subscribed'/>
>   </pubsub>
> </iq>

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to