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

correct retract to use pubsub syntax;

Browse Source
This commit is contained in:
Steve Kille 2018-12-11 08:27:48 +00:00
parent 444f690277
commit 291c69d45c
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
xep-0369.xml
View File

@ -45,6 +45,7 @@
fix retract id example; fix retract id example;
clarify that channels always created with default parameters; clarify that channels always created with default parameters;
change to reflect that XEP-0004 does not support multiple languages; change to reflect that XEP-0004 does not support multiple languages;
correct retract to use pubsub syntax;
editorial; editorial;
</p></remark> </p></remark>
</revision> </revision>
@ -1097,18 +1098,17 @@
</iq> </iq>
]]></example> ]]></example>
<p>When the user leaves the channel, the MIX service is responsible for unsubscribing the user from all nodes in the channel and for removing the user from the participants list. Presence removal is specified in MIX-PRESENCE. <p>When the user leaves the channel, the MIX service is responsible for unsubscribing the user from all nodes in the channel and for removing the user from the participants list. Presence removal is specified in MIX-PRESENCE.
Deletion from the participants node functions as if the item (channel participant) had been deleted using the PubSub retract mechanism with notification set to true. Notification of the participant deletion is sent to clients subscribed to the participants PubSub node, with the node identified by the stable id, as shown in the example below. Deletion from the participants node functions as if the item (channel participant) had been deleted using the PubSub retract mechanism with notification set to true. Notification of the participant deletion is sent to clients subscribed to the participants PubSub node using PubSub protocol, with the node identified by the stable id, as shown in the example below.
</p> </p>
<example caption="Reporting when User Leaves a Channel"><![CDATA[
<example caption="Participant Node Subscriber is Notified of Participant Removal"><![CDATA[
<message from='coven@mix.shakespeare.example' <message from='coven@mix.shakespeare.example'
to='hecate@shakespeare.example' id='f5pp2toz'> to='hecate@shakespeare.example' id='f5pp2toz'>
<event xmlns='http://jabber.org/protocol/pubsub#event'> <pubsub xmlns='http://jabber.org/protocol/pubsub'>
<items xmlns='urn:xmpp:mix:core:0' node='urn:xmpp:mix:nodes:participants'> <retract node='urn:xmpp:mix:nodes:participants'>
<item> <item id='123456'/>
<retract id='123456'/> </retract>
</item> </pubsub>
</items>
</event>
</message> </message>
]]></example> ]]></example>