moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-12-21 23:28:51 -05:00
Code Issues Releases Wiki Activity

Update 1:1 Conversion to history

Browse Source
This commit is contained in:
Steve Kille 2016-12-21 10:13:15 +00:00
parent 9e67e42df1
commit a0f67a4050
1 changed files with 18 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

23
xep-0369.xml
View File

@ -800,14 +800,13 @@ the participant is not be subscribed to all nodes associated with the channel (i
<event xmlns='http://jabber.org/protocol/pubsub#event'>
<items node='urn:xmpp:mix:nodes:participants'>
<item id='coven+123456@mix.shakespeare.example'>
<participant xmlns='urn:xmpp:mix:0'
nick='thirdwitch'/>
<participant xmlns='urn:xmpp:mix:0'/>
</item>
</items>
</event>
</message>
]]></example>
<p>The user that has been added to the channel is identified by the item id of the item added to the pubsub node, which is the proxy JID of the new channel participant. Each &lt;participant&gt; element will include the nick of the user being added, which will be how the user will typically be shown in the channel.</p>
<p>The user that has been added to the channel is identified by the item id of the item added to the pubsub node, which is the proxy JID of the new channel participant. Note that the &lt;participant&gt; element does not include a nick of the user being added. The nick MAY be set after the join.</p>
<p>
A user may subsequently modify subscription to nodes in a channel by sending a subscription modification request, as shown in the following example.
</p>
@ -1705,15 +1704,29 @@ A client creates a channel by sending a simple request to the MIX service. A c
</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.
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.
</p>
<p>
It may also be useful to share some or all of the messages from the 1:1 discussion into the new channel. The mechanism to do this is to have a special message format that includes information on the original message.
This will generally be done by the user creating the channel before the other user is invited, but may be sent by either the user creating the channel or the 1:1 chat partner at any time.
These messages are marked as &lt;resend&gt; which includes an number of parameters facilitate appropriate display of this selected chat history. This has the following parameters:
</p>
<ul>
<li>'time': the original message time.</li>
<li>'from': the original sender.</li>
<li>'to': the original recipient.</li>
</ul>
<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'/>
<resend xmlns='urn:xmpp:mix:0'
time='2010-07-10T23:08:25Z'
from='hag67@shakespeare.example/pda'
to='hag66@shakespeare.example/pda'
</resend>
</message>
]]></example>
</section3>