From 5f99de94e6689d678f5e57c88695a961c92e9fdf Mon Sep 17 00:00:00 2001 From: Steve Kille Date: Tue, 15 May 2018 16:19:13 +0100 Subject: [PATCH] more edits --- xep-0369-PAM.xml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/xep-0369-PAM.xml b/xep-0369-PAM.xml index 24fe6a4e..d9cddb2e 100644 --- a/xep-0369-PAM.xml +++ b/xep-0369-PAM.xml @@ -427,7 +427,7 @@ This approach enables flexible support of multiple clients for a MIX channel pa

The user's server will then pass this on to all online clients, with 'from' unchanged and 'to' set to the client receiving presence. An example is shown below:

- + @@ -436,10 +436,13 @@ This approach enables flexible support of multiple clients for a MIX channel pa ]]>

- The user's local server will will receive a flow of all presence updates for the user. It will pass this presence information on to all online clients. This ensures that an online client is kept updated with presence. + The user's local server will receive a flow of all presence updates for the user. It will pass this presence information on to all online clients. This ensures that an online client is kept updated with presence. When a client goes offline, it will cease getting presence updates. Presence updates will continue to flow to the user's local server, and so the local server is able maintain up to date presence state for the channel, even when there are no online clients. When a user had no online clients the user's server MAY continue to maintain MIX presence status for the user or MAY discard inbound MIX presence information.

+

+ The client receiving the presense can parse the proxy JID, specfied in MIX-CORE to identify the channel to which the message relates. The proxy JID can be looked up in the Participant's node to determine Nick and real bare JID. The real bare JID can be combined with the resource form the presense stanze to determine the full real JID of the sender. This is described in MIX-CORE. +