1.1.1
2024-02-20
@@ -321,7 +333,9 @@
from='romeo@montague.lit/orchard'
type='chat'>
Call me but love, and I'll be new baptized; Henceforth I never will be Romeo.
-
+
]]>
Note: Previous versions of this protocol did not specify any interaction with stanza-id, and clients MUST NOT interpret XEP-0359 IDs in messages as archive IDs unless the server advertises support for 'urn:xmpp:mam:2' specifically.
@@ -644,9 +658,9 @@
+ to='juliet@capulet.lit/balcony'
+ from='romeo@montague.lit/orchard'
+ type='chat'>
Call me but love, and I'll be new baptized; Henceforth I never will be Romeo.
@@ -658,9 +672,9 @@
+ to='romeo@montague.lit/orchard'
+ from='juliet@capulet.lit/balcony'
+ type='chat' id='8a54s'>
What man art thou that thus bescreen'd in night so stumblest on my counsel?
@@ -724,14 +738,14 @@
-
- urn:xmpp:mam:2
- 2010-08-07T00:00:00Z
-
-
- 10
- 09af3-cc343-b409f
-
+
+ urn:xmpp:mam:2
+ 2010-08-07T00:00:00Z
+
+
+ 10
+ 09af3-cc343-b409f
+
]]>
@@ -742,7 +756,7 @@
-
+
]]>
When the results returned by the server are complete (that is: when they have not been limited by the maximum size of the result page (either as specified or enforced by the server)), the server MUST include a 'complete' attribute on the <fin> element, with a value of 'true'; this informs the client that it doesn't need to perform further paging to retreive the requested data. If it is not the last page of the result set, the server MUST either omit the 'complete' attribute, or give it a value of 'false'.
@@ -765,14 +779,14 @@
-
- urn:xmpp:mam:2
- 2010-08-07T00:00:00Z
-
-
- 10
-
-
+
+ urn:xmpp:mam:2
+ 2010-08-07T00:00:00Z
+
+
+ 10
+
+
]]>
@@ -786,15 +800,15 @@
-
- urn:xmpp:mam:2
- 2010-08-07T00:00:00Z
-
-
- 10
- 09af3-cc343-b409f
-
-
+
+ urn:xmpp:mam:2
+ 2010-08-07T00:00:00Z
+
+
+ 10
+ 09af3-cc343-b409f
+
+
]]>
@@ -853,17 +867,17 @@
In the case of non-anonymous rooms or if the recipient of the MUC archive has the right to access the sender real JID at the time of the query, the archive message will use extended message information in an <x/> element qualified by the 'http://jabber.org/protocol/muc#user' namespace and containing an <item/> child with a 'jid' attribute specifying the occupant's full JID, as defined for non-anonymous room presence in &xep0045;. The archiving entity MUST strip any pre-existing <x> element from MUC messages (as MUC rooms are not required to do this).
-
+
+ from='coven@chat.shakespeare.lit/firstwitch'
+ id='162BEBB1-F6DB-4D9A-9BD8-CFDCC801A0B2'
+ type='groupchat'>
Thrice the brinded cat hath mew'd.
-