mirror of
https://github.com/moparisthebest/xeps
synced 2024-08-13 16:53:48 -04:00
Remove comments from examples in MAM
This commit is contained in:
parent
cf64b48a65
commit
8afa00d15b
26
xep-0313.xml
26
xep-0313.xml
@ -130,7 +130,7 @@
|
||||
<p>The most typical address is that of a user's own bare JID, within which those messages sent to or from that
|
||||
user's account would generally automatically be stored by the server. The collection
|
||||
is ordered chronologically by the time each message was sent/received.</p>
|
||||
|
||||
|
||||
<p>Servers that expose archive messages on behalf of local users MUST expose these archives to the user on the user's bare JID</p>
|
||||
</section2>
|
||||
<section2 topic='MUC archives' anchor='archives_user'>
|
||||
@ -158,18 +158,20 @@
|
||||
<example caption='A user queries their archive for messages'><![CDATA[
|
||||
<iq type='set' id='juliet1'>
|
||||
<query xmlns='urn:xmpp:mam:0' queryid='f27' />
|
||||
</iq>
|
||||
</iq>]]></example>
|
||||
|
||||
<!-- server accepts the query -->
|
||||
<iq type='result' id='juliet1'/>
|
||||
<example caption='Their server accepts the query'><![CDATA[
|
||||
<iq type='result' id='juliet1'/>]]></example>
|
||||
|
||||
<!-- server sends matching messages ... -->
|
||||
|
||||
<!-- final message -->
|
||||
<example caption='Their server sends the matching messages'><![CDATA[
|
||||
<message from="witch@shakespeare.lit" to="macbeth@shakespeare.lit">
|
||||
<body>Hail to thee</body>
|
||||
</message>]]></example>
|
||||
|
||||
<example caption='Server returns the message sentinel'><![CDATA[
|
||||
<message>
|
||||
<fin xmlns='urn:xmpp:mam:0' queryid='f27' />
|
||||
</message>
|
||||
]]></example>
|
||||
</message>]]></example>
|
||||
<p>To ensure that the client knows when the results are complete, the server MUST send a <fin> message. The client can optionally include a 'queryid' attribute in their query, which allows the client to match results to their initiating query, and if present in the client's query the server MUST include it in the <fin> response.</p>
|
||||
<p>When querying a pubsub node's archive, the 'node' attribute is added to the <query> element.</p>
|
||||
<example caption="A user queries a pubsub node's archive for messages"><![CDATA[
|
||||
@ -245,7 +247,7 @@
|
||||
</x>
|
||||
</query>
|
||||
</iq>
|
||||
]]></example>
|
||||
]]></example>
|
||||
<example caption='Querying the archive for all messages after a certain time'><![CDATA[
|
||||
<iq type='set' id='juliet1'>
|
||||
<query xmlns='urn:xmpp:mam:0'>
|
||||
@ -302,7 +304,7 @@
|
||||
]]></example>
|
||||
<p>The <first> and <last> elements specify the UID of the first and last returned
|
||||
results (not necessarily of all the messages that matched the query, if the results have been limited).</p>
|
||||
|
||||
|
||||
<p>The RSM <count> element and the 'index' attribute on the RSM <first> element are optional,
|
||||
but servers SHOULD include them. Please refer to the RSM specification for more information
|
||||
surrounding their meaning and use.</p>
|
||||
@ -566,7 +568,7 @@
|
||||
the standard 'feature-not-implemented' (the server does not support configuration of preferences),
|
||||
'forbidden' (the user is not authorized to change their preferences) or 'not-allowed' (the server
|
||||
generally does not allow changing of configuration preferences).</p>
|
||||
|
||||
|
||||
<section3 topic='Default behaviour' anchor='config-default'>
|
||||
<p>If a JID is in neither the 'always archive' nor the 'never archive' list then whether it
|
||||
is archived depends on this setting, the default.
|
||||
|
Loading…
Reference in New Issue
Block a user