From 8f684ace2b01652d4fee93e6f267ca9dd98ba488 Mon Sep 17 00:00:00 2001 From: Georg Lukas Date: Wed, 23 Aug 2017 16:20:37 +0200 Subject: [PATCH] XEP-0045: Clarify wording for a client re-syncing to a MUC TL;DR: whenever a client (re)sends a join, the MUC service should return everything a newly joining client needs to know. Discussion in https://mail.jabber.org/pipermail/standards/2016-June/031180.html --- xep-0045.xml | 1 + 1 file changed, 1 insertion(+) diff --git a/xep-0045.xml b/xep-0045.xml index 6a496107..b3a2710c 100644 --- a/xep-0045.xml +++ b/xep-0045.xml @@ -1385,6 +1385,7 @@ ]]>

Before attempting to enter the room, a MUC-compliant client SHOULD first discover its reserved room nickname (if any) by following the protocol defined in the Discovering Reserved Room Nickname section of this document.

+

When a MUC service receives an <x/> tagged join stanza from an already-joined client (as identified by the client's full JID), the service SHOULD assume that the client lost its synchronization, and therefore it SHOULD send exactly the same stanzas to the client as if it would actually join the MUC. The server MAY also send a presence update to the other participants according to the received join presence.