mirror of
https://github.com/moparisthebest/xeps
synced 2024-12-21 15:18:51 -05:00
typo
This commit is contained in:
parent
885720147c
commit
eef60ad67b
@ -129,7 +129,7 @@
|
||||
<section1 topic='When to Request Receipts' anchor='when'>
|
||||
<p>A sender <em>could</em> request receipts on any non-error content message (chat, groupchat, headline, or normal) no matter if the recipient's address is a bare JID &LOCALBARE; or a full JID &LOCALFULL;. Whether it is <em>appropriate</em> or <em>advisable</em> to do so it another question. This section provides recommendations about when and when not to request receipts, and what results to expect in each scenario.</p>
|
||||
<section2 topic='Bare JID' anchor='when-bare'>
|
||||
<p>If the sender knows only the recipient's bare JID, it cannot cannot determine (via &xep0030; or &xep0115;) whether the intended recipient supports the Message Delivery Receipts protoocl. In this case, the sender MAY request a receipt when sending a content message of type "chat", "headline", or "normal" to the recipient's bare JID. However, the sender MUST NOT depend on receiving an ack message in reply.</p>
|
||||
<p>If the sender knows only the recipient's bare JID, it cannot determine (via &xep0030; or &xep0115;) whether the intended recipient supports the Message Delivery Receipts protocol. In this case, the sender MAY request a receipt when sending a content message of type "chat", "headline", or "normal" to the recipient's bare JID. However, the sender MUST NOT depend on receiving an ack message in reply.</p>
|
||||
</section2>
|
||||
<section2 topic='Full JID' anchor='when-full'>
|
||||
<p>If the sender knows a full JID for the recipient (e.g., via presence), it SHOULD attempt to determine (via service disco or entity capabilities) whether the client at that full JID supports the Message Delivery Receipts protocol before attempting to request receipts.</p>
|
||||
|
Loading…
Reference in New Issue
Block a user