From 252d86b905b93f94e247b24c70a1bcb35848a19d Mon Sep 17 00:00:00 2001 From: Steve Kille Date: Tue, 10 Jan 2017 11:54:29 +0000 Subject: [PATCH] Add node=mix to enable MUC/MIX co-existence --- xep-0369.xml | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/xep-0369.xml b/xep-0369.xml index d4d84e5f..dddfbd10 100644 --- a/xep-0369.xml +++ b/xep-0369.xml @@ -2103,7 +2103,7 @@ A client creates a channel by sending a simple request to the MIX service. A c
  • Fully integrated MIX and MUC implementation, with MIX and MUC sharing a single domain and rooms/channels equivalent.
  • Partially integrated MIX and MUC implementation, with MIX and MUC using separate domains, but rooms/channel are common. This means that each MIX channel will have MUC room of the same name and same participants.
    • -

    The fully integrated approach would be transparent to clients. Disco of a room or channel would show support for both MUC and MIX, which would enable a client to choose whether to use MUC or MIX. The following example shows how a MIX service that also supported MUC would respond:

    +

    The fully integrated approach would be transparent to clients. The following example shows how a MIX service that also supported MUC would respond:

    ]]> +

    In the fully integrated service item discovery on the MIX/MUC service determines a list of channels. The protocol used for this is the same in MUC and MIX. Discovery actions on a channel in MIX will use 'node=mix' in the discovery which will lead to the return of MIX channel specific information. If is not set, MUC room specific information is returned. +

    For the partially integrated service, it will be useful for clients that support both MIX and MUC to be able to determine that the server supports both protocols. For a MIX client, it will be useful to know the MUC service, so that this information can be shared with a MUC client invitation. This information is provided by the initial service discovery:

    The result is returned in an extended disco results in a form whose type value is 'urn:xmpp:mix:0#serviceinfo'. The field with var='muc-mirror' is the value of which is the mirrored MUC domain's JID.

    Where a client supporting both MIX and MUC is given a reference to a MUC room, it is desirable that the client can determine the MIX channel and join using MIX. This is achieved by an equivalent extension to MUC service discover.

    -