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

Make Archiving Optional;

Browse Source
This commit is contained in:
Steve Kille 2019-03-19 08:46:19 +00:00
parent 97104b2bb3
commit f31e54e29b
1 changed files with 13 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
xep-0405.xml
View File

@ -38,11 +38,19 @@
<shortname>MIX-PAM</shortname>
&ksmithisode;
&skille;
<revision>
<version>0.4.0</version>
<date>2019-03-19</date>
<initials>sek</initials>
<remark>
Make Archiving Optional;
</remark>
</revision>
<revision>
<version>0.3.1</version>
<date>2019-01-13</date>
<initials>lnj (Editor: jsc)</initials>
<remark>Whitespace changes and XML syntax fixes</remark>
<remark>White space changes and XML syntax fixes</remark>
</revision>
<revision>
<version>0.3.0</version>
@ -186,7 +194,7 @@ This approach enables flexible support of multiple clients for a MIX channel pa
<section2 topic="Client Determines MIX Capability of Client's Server" anchor="user-server-client-capability">
<p>
Servers supporting this specification MUST advertise this to clients for which they wish to support this specification. A client wishing to use MIX MUST check for this capability in the local server before using MIX, by verifying support for the client's account. The capability is represented by the 'urn:xmpp:mix:pam:0' feature.
Servers supporting this specification MUST advertise this to clients for which they wish to support this specification. A client wishing to use MIX MUST check for this capability in the local server before using MIX, by verifying support for the client's account. The capability is represented by the 'urn:xmpp:mix:pam:0' feature. In addition to this the server MAY advertize the 'urn:xmpp:mix:pam:0#archive' feature, which shows that the local server archives MIX messages.
</p>
<example caption="Client Determines MIX Capability for Server Account"><![CDATA[
<iq from='hag66@shakespeare.example/UUID-c8y/1573'
@ -200,6 +208,7 @@ This approach enables flexible support of multiple clients for a MIX channel pa
type='result'>
<query xmlns='http://jabber.org/protocol/disco#info'>
<feature var='urn:xmpp:mix:pam:0'/>
<feature var='urn:xmpp:mix:pam:0:archive'/>
</query>
</iq>
]]></example>
@ -514,7 +523,8 @@ This approach enables flexible support of multiple clients for a MIX channel pa
<section2 topic="MAM Archive Support" anchor="usecase-mam">
<p>
Archive of MIX channel messages is done by the participant's server. Where a message is sent to the participant's server and discarded because there are no active clients, it will still be archived. This means that the messages will be available in the local archive and can be picked up by clients when they come online.
Archive of MIX channel messages MAY be performed by the participant's server. When this is done, the capability is advertized to MIX clients using the 'urn:xmpp:mix:pam:0#archive' feature. If archive is provided it MUST always be used, so that
where a message is sent to the participant's server and discarded because there are no active clients, it will still be archived. This means that when archiving is provided, the messages will be available in the local archive and can be picked up by clients when they come online.
</p>
</section2>