moparisthebest
/
xeps
mirror of https://github.com/moparisthebest/xeps
1
0
Fork 0
Code Issues Releases Wiki Activity

Corrections

This commit is contained in:
Steve Kille 2017-06-13 15:04:35 +01:00
parent bee049fbef
commit 39611ada6f
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
xep-0369.xml
View File

@ -2528,7 +2528,7 @@ This approach enables flexible support of multiple clients for a MIX channel pa
]]></example> ]]></example>
<p> <p>
MIX channels in the roster have an empty element 'channel' included in the roster item. MIX channels in the roster have an element 'channel' included in the roster item.
</p> </p>
<example caption="Roster Item Encoding of a MIX Channel"><![CDATA[ <example caption="Roster Item Encoding of a MIX Channel"><![CDATA[
@ -2538,7 +2538,7 @@ This approach enables flexible support of multiple clients for a MIX channel pa
]]></example> ]]></example>
<p> <p>
A server following the MIX specification MUST determine whether or not a client supports MIX. The server will often have this information prior to the roster request, due to &xep0115; Entity Capabilities. If the server does not have this information it MUST use service discovery to determine it before providing roster information. A server following the MIX specification MUST determine whether or not a client supports MIX. If the server does not have this information it MUST use service discovery to determine it before providing roster information.
When sending roster information to a client that advertises MIX capability, the server MUST return all MIX channels and MUST use this encoding. Presence of MIX roster items MUST be set to offline (unavailable). When sending roster information to a client that advertises MIX capability, the server MUST return all MIX channels and MUST use this encoding. Presence of MIX roster items MUST be set to offline (unavailable).
</p> </p>
@ -2547,7 +2547,7 @@ This approach enables flexible support of multiple clients for a MIX channel pa
</p> </p>
<p> <p>
When a server determines that a client has added or removed MIX capability, the entire roster MUST be sent and roster version reset. This is not a particularly efficient approach, but this is expected to be a rare event and so a simple approach is preferred. When a client adds MIX capability, additional information needs to be provided by the server. To support this, a server MUST maintain information about client MIX support status. When a server detects this change it needs to update the roster which it MAY do incrementally or by sending all of the roster.
</p> </p>
</section2> </section2>