further text clarification

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1893 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2008-05-29 19:24:56 +00:00
parent f7edffd982
commit 4d555759c8
1 changed files with 1 additions and 1 deletions

View File

@ -176,7 +176,7 @@
</query>
</iq>
]]></code>
<p>At this point, your client knows that a contact who advertises a version string of 'QgayPKawpkPSDYmwT/WM94uAlu0=' supports &xep0045; and the other features returned by Romeo because the contact in fact uses the same client software as Romeo. (The string can be relied upon because of how it is generated and checked, as explained later in this document.) Your client remembers this information, so that it does not need to explicitly query the capabilities of a contact with the same version string. For example, your Nurse may use the same client that Romeo does:</p>
<p>At this point, your client knows that a contact who advertises a version string of 'QgayPKawpkPSDYmwT/WM94uAlu0=' supports &xep0045; and the other features returned by Romeo because the contact in fact uses the same version of the same client software as Romeo, with the same enabled features, plugins, presented client name(s), and the like (i.e., the same input to the verification string <link url='#ver-gen'>generation method</link>). <note>The string can be relied upon because of how it is generated and checked, as explained later in this document.</note> Your client remembers this information, so that it does not need to explicitly query the capabilities of a contact with the same version string. For example, your Nurse may use the same client that Romeo does:</p>
<code><![CDATA[
<presence from='nurse@capulet.lit/chamber'>
<c xmlns='http://jabber.org/protocol/caps'