Clarify distinguishing channels in roster

This commit is contained in:
Steve Kille 2017-01-30 16:22:51 +00:00 committed by Sam Whited
parent 9f9bae5092
commit 2b7c5f4e28
1 changed files with 3 additions and 0 deletions

View File

@ -2238,6 +2238,9 @@ the participant is not be subscribed to all nodes associated with the channel (i
<p> <p>
The participant's server SHOULD ensure that only presence information from activated MIX clients is sent to the MIX channel. So, if a user has two online clients, but only one is activated for a given MIX channel, then the channel SHOULD only receive presence information relating to the activated client. The participant's server SHOULD ensure that only presence information from activated MIX clients is sent to the MIX channel. So, if a user has two online clients, but only one is activated for a given MIX channel, then the channel SHOULD only receive presence information relating to the activated client.
</p> </p>
<p>
In order to present channels usefully to the end user a client MAY disco the domain of a roster entry to discover if it is a MIX service. As MIX services MUST NOT support end users, this information MAY be cached help the client distinguish MIX channels in the roster.
</p>
</section2> </section2>
<section2 topic="MAM Archive Support" anchor="proxy-mam"> <section2 topic="MAM Archive Support" anchor="proxy-mam">