moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-24 10:12:19 -05:00
Code Issues Releases Wiki Activity

XEP-0163: Release version 1.2.2

Browse Source 
Add comma and fix typo
This commit is contained in:
Melvin Keskin 2022-02-16 15:18:51 +01:00
parent 17f235c3da
commit cf6ac3e6c5
No known key found for this signature in database
GPG Key ID: 04EFAD0F7A4D9724
1 changed files with 7 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
xep-0163.xml
View File

@ -26,6 +26,12 @@
<shortname>pep</shortname> <shortname>pep</shortname>
&stpeter; &stpeter;
&ksmith; &ksmith;
<revision>
<version>1.2.2</version>
<date>2022-02-16</date>
<initials>melvo</initials>
<remark><p>Add comma and fix typo</p></remark>
</revision>
<revision> <revision>
<version>1.2.1</version> <version>1.2.1</version>
<date>2018-03-18</date> <date>2018-03-18</date>
@ -406,7 +412,7 @@
</ol> </ol>
</section3> </section3>
<section3 topic='Sending the Last Published Item' anchor='notify-last'> <section3 topic='Sending the Last Published Item' anchor='notify-last'>
<p>As mentioned, a PEP service MUST send the last published item to all new subscribers and to all newly-available resources for each subscriber, including the account owner itself. (That is, the default value of the "pubsub#send_last_published_item" node configuration field must be "on_sub_and_presence"; this behavior essentially mimics the functionality of presence as defined in <cite>XMPP IM</cite>.) When processing a new subscription, the service MAY send not only the last published item but instead all items that are currently associated with the node (i.e., up to the maximum number of items at the node, which might be one if the node is a "singleton node" as described in <cite>XEP-0060</cite>). If the service has knowledge about the datetime that a subscriber's newly-available resource last received updated information from the node (e.g., as described in &xep0256;) then it MAY also send more items that only the last published item to the newly-available resource.</p> <p>As mentioned, a PEP service MUST send the last published item to all new subscribers and to all newly-available resources for each subscriber, including the account owner itself. (That is, the default value of the "pubsub#send_last_published_item" node configuration field must be "on_sub_and_presence"; this behavior essentially mimics the functionality of presence as defined in <cite>XMPP IM</cite>.) When processing a new subscription, the service MAY send not only the last published item but instead all items that are currently associated with the node (i.e., up to the maximum number of items at the node, which might be one if the node is a "singleton node" as described in <cite>XEP-0060</cite>). If the service has knowledge about the datetime that a subscriber's newly-available resource last received updated information from the node (e.g., as described in &xep0256;), then it MAY also send more items than only the last published item to the newly-available resource.</p>
<p class='box'>Note: The "on_sub_and_presence" setting relates to the <em>subscriber's</em> presence, not the publisher's presence.</p> <p class='box'>Note: The "on_sub_and_presence" setting relates to the <em>subscriber's</em> presence, not the publisher's presence.</p>
<example caption='Subscriber sends presence from newly-available resource'><![CDATA[ <example caption='Subscriber sends presence from newly-available resource'><![CDATA[
<presence from='romeo@montague.lit/orchard'> <presence from='romeo@montague.lit/orchard'>