From 4a4502c420f9704c7ac36133c8291f9e6d93b171 Mon Sep 17 00:00:00 2001 From: Steve Kille Date: Fri, 4 Nov 2016 15:45:48 +0000 Subject: [PATCH] Conversion 1:1 --- xep-0369.xml | 27 ++++++++++++++++++--------- 1 file changed, 18 insertions(+), 9 deletions(-) diff --git a/xep-0369.xml b/xep-0369.xml index 73a1b746..2658763a 100644 --- a/xep-0369.xml +++ b/xep-0369.xml @@ -1829,10 +1829,25 @@ A client creates a channel by sending a simple request to the MIX service. A c ]]> + + + +

+ A common use case for an ad hoc channel is where two users are engaged in a 1:1 chat and wish to broaden the discussion. Prior to bringing more users into a channel, using standard invitation process, there is a need to move a dialogue. The first step is for one of the two users to create an ad hoc channel, as described in the previous section. The other user will then be invited, and can switch to the new channel. It may also be useful to share some or all of the messages from the 1:1 discussion into the new channel. This is done by sending these messages to the channel. These messages are marked as <resend> which includes the original message time to facilitate appropriate display. +

+ + + Harpier cries: 'tis time, 'tis time. + + +]]> + + - - -

MIX channels are always explicitly destroyed by an owner of the channel or by a server operator. There is no concept of temporary channel, equivalent to &xep0045; temporary room which is automatically destroyed by the server when the users leave. However, channels MAY be configured with an explicit lifetime, after which the channel MUST be removed by the MIX server. Where a channel is created for ad hoc use, it may be desirable to keep the channel for history reference or for re-use by the same set of users. Note that the owner of the channel does not need to have presence registered in the channel in order to destroy it. @@ -2226,13 +2241,7 @@ A client creates a channel by sending a simple request to the MIX service. A c

- -

- &xep0045; describes how to convert from a 1:1 chat to a MUC room. Conversion from 1:1 chat is a straightforward and useful capability, that is not described in this version of the MIX specification. This capability may be added in a future version of this XEP or as separate XEP. - -

-