mirror of
https://github.com/moparisthebest/xeps
synced 2024-11-22 01:02:17 -05:00
added service discovery use case
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1110 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
parent
303b44c9ec
commit
c397fef7af
24
xep-0066.xml
24
xep-0066.xml
@ -150,6 +150,30 @@
|
|||||||
</message>
|
</message>
|
||||||
]]></example>
|
]]></example>
|
||||||
</section1>
|
</section1>
|
||||||
|
<section1 topic='Determining Support' anchor='disco'>
|
||||||
|
<p>If an entity supports the out of band data protocol, it MUST report that by including a service discovery feature of "jabber:iq:oob" and/or "jabber:x:oob" in response to a &xep0030; information request:</p>
|
||||||
|
<example caption="Service Discovery information request"><![CDATA[
|
||||||
|
<iq type='get'
|
||||||
|
from='juliet@capulet.lit/balcony'
|
||||||
|
to='romeo@montague.lit/orchard'
|
||||||
|
id='disco1'>
|
||||||
|
<query xmlns='http://jabber.org/protocol/disco#info'/>
|
||||||
|
</iq>
|
||||||
|
]]></example>
|
||||||
|
<example caption="Service Discovery information response"><![CDATA[
|
||||||
|
<iq type='result'
|
||||||
|
from='romeo@montague.lit/orchard'
|
||||||
|
to='juliet@capulet.lit/balcony'
|
||||||
|
id='disco1'>
|
||||||
|
<query xmlns='http://jabber.org/protocol/disco#info'>
|
||||||
|
...
|
||||||
|
<feature var='jabber:iq:oob'/>
|
||||||
|
<feature var='jabber:x:oob'/>
|
||||||
|
...
|
||||||
|
</query>
|
||||||
|
</iq>
|
||||||
|
]]></example>
|
||||||
|
</section1>
|
||||||
<section1 topic='Use With Non-HTTP URI Schemes' anchor='nonhttp'>
|
<section1 topic='Use With Non-HTTP URI Schemes' anchor='nonhttp'>
|
||||||
<p>The value of the <url/> element is not limited to URIs that conform to the http: URI scheme (as specified by &rfc2616;). For example, file transfers could also be effected using ftp: URIs as (specified by &rfc0959;). Going further afield, several existing Jabber clients use the callto: URI scheme to initiate voice conferencing via NetMeeting or GnomeMeeting. Other out-of-band communications could be initiated in a similar way via URI schemes such as sip: (as specified by &rfc3261;). All of these usages are allowed by the existing OOB namespaces, as long as the value of the <url/> element is a valid URI (as specified by &rfc3986;).</p>
|
<p>The value of the <url/> element is not limited to URIs that conform to the http: URI scheme (as specified by &rfc2616;). For example, file transfers could also be effected using ftp: URIs as (specified by &rfc0959;). Going further afield, several existing Jabber clients use the callto: URI scheme to initiate voice conferencing via NetMeeting or GnomeMeeting. Other out-of-band communications could be initiated in a similar way via URI schemes such as sip: (as specified by &rfc3261;). All of these usages are allowed by the existing OOB namespaces, as long as the value of the <url/> element is a valid URI (as specified by &rfc3986;).</p>
|
||||||
</section1>
|
</section1>
|
||||||
|
Loading…
Reference in New Issue
Block a user