From e56fc624a19e3a34388d246b2c70c44ad11c45f3 Mon Sep 17 00:00:00 2001 From: Georg Lukas Date: Tue, 15 Jan 2019 17:26:10 +0100 Subject: [PATCH] XEP-0410: mention 0198 and explicit re-join --- xep-0410.xml | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/xep-0410.xml b/xep-0410.xml index e1f87f4c..11a7c9e7 100644 --- a/xep-0410.xml +++ b/xep-0410.xml @@ -61,7 +61,8 @@ protocol).

This specification aims to provide the most efficient, albeit not the most elegant, way for clients to periodically check whether they are still - joined to a chatroom.

+ joined to a chatroom. However, it can not ensure that a client remains + joined to a room without any interruptions.

This specification only makes sense in the context of &xep0045; @@ -158,7 +159,7 @@ joined, but the participant just changed their name (e.g. initiated by a different client).

  • Any other error: the client is probably not - joined.
    • + joined any more. It should perform a re-join.
  • Timeout (no response): the MUC service (or another client) is unreachable. The client may indicate the status to the user and re-attempt the self-ping after some timeout, until it receives @@ -198,6 +199,9 @@ change, and before receiving the response to the nickname change from the service, as it is not yet clear whether the new nickname will be accepted.

    +

    If a client session is in hibernation (&xep0198;), the client should defer + sending of self-ping requests until it is reconnected and re-authenticated. +

    A MUC service implementation should not allow a non-participant to obtain