moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-22 09:12:19 -05:00
Code Issues Releases Wiki Activity

Merge commit 'refs/pull/726/head' of https://github.com/xsf/xeps

Browse Source
This commit is contained in:
Jonas Schäfer 2018-12-13 19:32:32 +01:00
commit 46a4629174
1 changed files with 15 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
xep-0405.xml
View File

@ -38,6 +38,15 @@
<shortname>MIX-PAM</shortname> <shortname>MIX-PAM</shortname>
&ksmithisode; &ksmithisode;
&skille; &skille;
<revision>
<version>0.3.0</version>
<date>2018-12-11</date>
<initials>sek</initials>
<remark>
Discovery on Account rather than Server;
Add participant ID to roster;
</remark>
</revision>
<revision> <revision>
<version>0.2.1</version> <version>0.2.1</version>
<date>2018-11-03</date> <date>2018-11-03</date>
@ -179,19 +188,18 @@ This approach enables flexible support of multiple clients for a MIX channel pa
</section2> </section2>
<section2 topic="Client Determines MIX Capability of Local Server" anchor="user-server-client-capability"> <section2 topic="Client Determines MIX Capability of Client's Server" anchor="user-server-client-capability">
<p> <p>
Servers supporting this specification MUST advertise this to clients. A client wishing to use MIX MUST check for this capability in the local server before using MIX. The capability is represented by the 'urn:xmpp:mix:pam:0' feature. Servers supporting this specification MUST advertise this to clients for which they wish to support this specification. A client wishing to use MIX MUST check for this capability in the local server before using MIX, by verifying support for the client's account. The capability is represented by the 'urn:xmpp:mix:pam:0' feature.
</p> </p>
<example caption="Client Determines MIX Capability of Local Server"><![CDATA[ <example caption="Client Determines MIX Capability for Server Account"><![CDATA[
<iq from='hag66@shakespeare.example/UUID-c8y/1573' <iq from='hag66@shakespeare.example/UUID-c8y/1573'
id='lx09df27' id='lx09df27'
type='get'> type='get'>
<query xmlns='http://jabber.org/protocol/disco#info'/> <query xmlns='http://jabber.org/protocol/disco#info'/>
</iq> </iq>
<iq from='shakespeare.example' <iq id='lx09df27'
id='lx09df27'
to='hag66@shakespeare.example/UUID-c8y/1573' to='hag66@shakespeare.example/UUID-c8y/1573'
type='result'> type='result'>
<query xmlns='http://jabber.org/protocol/disco#info'> <query xmlns='http://jabber.org/protocol/disco#info'>
@ -534,12 +542,12 @@ This approach enables flexible support of multiple clients for a MIX channel pa
]]></example> ]]></example>
<p> <p>
MIX channels in the roster information returned in response to a request for this additional MIX information MUST have an element &lt;channel/&gt; qualified by the ‘urn:xmpp:mix:roster:0' namespace included in the roster item, as shown inf the following example. MIX channels in the roster information returned in response to a request for this additional MIX information MUST have an element &lt;channel/&gt; qualified by the ‘urn:xmpp:mix:roster:0' namespace included in the roster item. The &lt;channel/&gt; element MUST also include a 'participant-id' attribute that is the stable ID of the client. This facilitates the client to match messages that reference this stable ID. A MIX extended roster item is shown in the following example.
</p> </p>
<example caption="Roster Item Encoding of a MIX Channel"><![CDATA[ <example caption="Roster Item Encoding of a MIX Channel"><![CDATA[
<item jid='balcony@example.net'> <item jid='balcony@example.net'>
<channel xmlns='urn:xmpp:mix:roster:0'/> <channel xmlns='urn:xmpp:mix:roster:0' participant-id='123456'/>
</item> </item>
]]></example> ]]></example>