moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-21 16:55:07 -05:00
Code Issues Releases Wiki Activity

1.2 published

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@599 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2007-02-16 06:12:39 +00:00
parent a037ddd440
commit e642a594a8
1 changed files with 29 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

37
xep-0012.xml
View File

@ -27,40 +27,40 @@
&temas;
&stpeter;
<revision>
<version>1.2pre1</version>
<date>in progress, last updated 2007-02-09</date>
<version>1.2</version>
<date>2007-02-15</date>
<initials>psa</initials>
<remark>Per a vote of the XMPP Council, changed from Historical and Active to Standards Track and Draft; added Implementation Notes and clarified text throughout; added proviso to security considerations regarding client support.</remark>
<remark><p>Per a vote of the XMPP Council, changed from Historical and Active to Standards Track and Draft; added Implementation Notes and clarified text throughout; added proviso to security considerations regarding client support; added section on Service Discovery.</p></remark>
</revision>
<revision>
<version>1.1</version>
<date>2004-01-22</date>
<initials>psa</initials>
<remark>Editorial revisions.</remark>
<remark><p>Editorial revisions.</p></remark>
</revision>
<revision>
<version>1.0</version>
<date>2002-01-22</date>
<initials>psa</initials>
<remark>Changed status to Active.</remark>
<remark><p>Changed status to Active.</p></remark>
</revision>
<revision>
<version>0.3</version>
<date>2002-01-14</date>
<initials>psa</initials>
<remark>Made appropriate changes to reflect status as informational.</remark>
<remark><p>Made appropriate changes to reflect status as informational.</p></remark>
</revision>
<revision>
<version>0.2</version>
<date>2002-01-04</date>
<initials>tjm</initials>
<remark>Converted to XML format.</remark>
<remark><p>Converted to XML format.</p></remark>
</revision>
<revision>
<version>0.1</version>
<date>2001-01-25</date>
<initials>jm</initials>
<remark>Initial version from website.</remark>
<remark><p>Initial version from website.</p></remark>
</revision>
</header>
<section1 topic='Introduction' anchor='intro'>
@ -132,6 +132,27 @@
]]></example>
<p>In this example, the server has been up for a little more than 34 hours.</p>
</section1>
<section1 topic='Determining Support' anchor='disco'>
<p>In order for a requesting entity to determine if a responding entity supports result set management, it SHOULD send a &xep0030; information request to the responding entity:</p>
<example caption='Requesting entity queries responding entity regarding protocol support'><![CDATA[
<iq from='stpeter@jabber.org/roundabout'
to='jabber.org'
id='disco1'>
<query xmlns='http://jabber.org/protocol/disco#info'/>
</iq>
]]></example>
<example caption='Responding entity communicates protocol support'><![CDATA[
<iq from='jabber.org'
to='stpeter@jabber.org/roundabout'
id='disco1'>
<query xmlns='http://jabber.org/protocol/disco#info'>
...
<feature var='jabber:iq:last'/>
...
</query>
</iq>
]]></example>
</section1>
<section1 topic='Implementation Notes' anchor='impl'>
<p>The information contained in an IQ reply for this namespace is inherently aambiguous. Specifically, for a bare JID (&BAREJID;) the information is the time since the JID was last connected to its server; for a full JID (&FULLJID;) the information is the time since the resource was last active in the context of an existing session; and for a bare domain the information is the uptime for the server or component. An application must take these differences into account when presenting the information to a human user.</p>
</section1>