[
https://issues.apache.org/jira/browse/VYSPER-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Jakl resolved VYSPER-51.
--------------------------------
Resolution: Fixed
Fixed with rev789126.
* Make LeafNodes disco#info discoverable
* Removed name of the root-collection node
* Made nodes available via their name instead of the full JID
* Removed the need for a JID within a LeafNode (name is unique)
> Discovery for Leaf Nodes (XEP-0060 5.3)
> ---------------------------------------
>
> Key: VYSPER-51
> URL: https://issues.apache.org/jira/browse/VYSPER-51
> Project: VYSPER
> Issue Type: Sub-task
> Components: XEP0060 PubSub
> Reporter: Michael Jakl
> Assignee: Michael Jakl
> Attachments: VYSPER-51.1.patch
>
>
> Quote XEP-0060 4.6: for discovery purposes, a pubsub node is equivalent to a
> Service Discovery node
> Discovery lies within the http://jabber.org/protocol/disco#info namespace.
> Example 15. Entity queries leaf node for information
> <iq type='get'
> from='[email protected]/barracks'
> to='pubsub.shakespeare.lit'
> id='info1'>
> <query xmlns='http://jabber.org/protocol/disco#info'
> node='princely_musings'/>
> </iq>
>
> Example 16. Service responds with identity of pubsub/leaf
> <iq type='result'
> from='pubsub.shakespeare.lit'
> to='[email protected]/barracks'
> id='info1'>
> <query xmlns='http://jabber.org/protocol/disco#info'
> node='princely_musings'>
> ...
> <identity category='pubsub' type='leaf'/>
> ...
> </query>
> </iq>
>
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.