diff --git a/xep-0160.xml b/xep-0160.xml index 034485b7..79d8a8ca 100644 --- a/xep-0160.xml +++ b/xep-0160.xml @@ -70,7 +70,7 @@ Too flattering-sweet to be substantial. - ]]> +]]>

Next, the recipient's server determines if there are any available resources that have sent non-negative presence priority. If there are, the server immediately delivers the message stanza to the resource that it determines to be most available (based on its own algorithm).

Next, the recipient's server determines if offline messages can be stored on behalf of the intended recipient. If not (e.g., because the recipient's offline message queue is full), the server returns a &unavailable; error to the sender. If so, the server stores the message for later delivery.

Now the recipient authenticates with the server and sends initial presence (with a non-negative priority) to the server.

@@ -78,7 +78,7 @@ 1 - ]]> +]]>

The recipient's server now delivers the offline message to that resource (it is RECOMMENDED for the server to add a &xep0203; extension to indicate that the message was stored offline).

@@ -91,7 +91,7 @@ from='capulet.com' stamp='2002-09-10T23:08:25Z'>Offline Storage - ]]> +]]>

Message stanzas SHOULD be handled by a server as follows (based on the values of the 'type' attribute specified in RFC 6121):

@@ -109,15 +109,16 @@ - ]]> +]]> ... + ... - ]]> +]]>

A message stored offline may not be readable by the recipient if the message was encrypted using a session-based encryption method such as &xep0116; or if the key used in object encryption is revoked after the message was sent but before it is read.