moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-08-13 16:53:48 -04:00
Code Issues Releases Wiki Activity

tweaks

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1480 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2007-12-18 23:00:42 +00:00
parent e991194765
commit e336a2054c
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
xep-0115.xml
View File

@ -356,7 +356,7 @@
ver='ItBTI0XLDFvVxZ72NQElAzKS9sU='> ver='ItBTI0XLDFvVxZ72NQElAzKS9sU='>
</stream:features> </stream:features>
]]></example> ]]></example>
<p>When a connected client or peer server sends a service discovery information request to determine the entity capabilities of a server that advertises capabilities via the stream feature, the requesting entity MUST send the disco#info request to the server's JID as provided in the 'from' attribute of the response stream header, if any (the 'from' attribute was recommended by &rfc3920; and is required by &rfc3920bis;).</p> <p>When a connected client or peer server sends a service discovery information request to determine the entity capabilities of a server that advertises capabilities via the stream feature, the requesting entity MUST send the disco#info request to the server's JID as provided in the 'from' attribute of the response stream header (the 'from' attribute was recommended by &rfc3920; and is required by &rfc3920bis;). To enable this functionality, a server that advertises support for entity capabilities MUST provide a 'from' address in its response stream headers, in accordance with <cite>rfc3921bis</cite>.</p>
</section2> </section2>
</section1> </section1>
@ -403,7 +403,7 @@
type='result'> type='result'>
<query xmlns='http://jabber.org/protocol/disco#info'> <query xmlns='http://jabber.org/protocol/disco#info'>
... ...
<feature var='http://jabber.org/protocol/caps'/> <feature var='http://jabber.org/protocol/caps#optimize'/>
... ...
</query> </query>
</iq> </iq>