1
0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-21 16:55:07 -05:00

Conversion 1:1

This commit is contained in:
Steve Kille 2016-11-04 15:45:48 +00:00 committed by Sam Whited
parent 47f33da419
commit 4a4502c420

View File

@ -1829,9 +1829,24 @@ A client creates a channel by sending a simple request to the MIX service. A c
<create channel='A1B2C345' xmlns='urn:xmpp:mix:0'/>
</iq>
]]></example>
</section3>
<section3 topic="Converting a 1:1 Conversation to a Channel" anchor="usecase-admin-converting-chat">
<p>
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 &lt;resend&gt; which includes the original message time to facilitate appropriate display.
</p>
<example caption="Resending a message to create History" ><![CDATA[
<message from='hag66@shakespeare.example/pda'
to='A1B2C345@mix.shakespeare.example'
id='92vax143g'
type='groupchat'>
<body>Harpier cries: 'tis time, 'tis time.</body>
<resend xmlns='urn:xmpp:mix:0' time='2010-07-10T23:08:25Z'/>
</message>
]]></example>
</section3>
<section3 topic='Destroying a Channel' anchor='usecase-admin-destroy'>
<p>
@ -2226,13 +2241,7 @@ A client creates a channel by sending a simple request to the MIX service. A c
</p>
</section2>
<section2 topic="Conversion from 1:1 Chat" anchor="chat-conversion">
<p>
&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.
</p>
</section2>
<section2 topic="Voice Control" anchor="voice-control">
<p>