moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-23 17:52:15 -05:00
Code Issues Releases Wiki Activity

added note about avoiding directed presence

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3582 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2009-10-29 16:49:33 +00:00
parent 5007de986b
commit dc6a14a5d3
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
xep-0163.xml
View File

@ -11,6 +11,7 @@
&LEGALNOTICE;
<number>0163</number>
<status>Draft</status>
<interim/>
<type>Standards Track</type>
<sig>Standards JIG</sig>
<approver>Council</approver>
@ -27,10 +28,10 @@
&stpeter;
&ksmith;
<revision>
<version>1.2rc3</version>
<date>in progress, last updated 2009-09-18</date>
<version>1.2rc4</version>
<date>in progress, last updated 2009-10-29</date>
<initials>psa</initials>
<remark><p>Removed the one-node-per-namespace rule (community consensus indicates that this rule was overly restrictive); clarified the meaning of auto-subscribe; clarified that sending the last published item does not prevent the service from sending additional items in some circumstances.</p></remark>
<remark><p>Removed the one-node-per-namespace rule (community consensus indicates that this rule was overly restrictive); clarified the meaning of auto-subscribe; clarified that sending the last published item does not prevent the service from sending additional items in some circumstances; discouraged the use of directed presence for the purpose of implicit subscriptions.</p></remark>
</revision>
<revision>
<version>1.1</version>
@ -328,6 +329,7 @@
<li>A service automatically sends notifications to all of the account owner's connected resources (subject to notification filtering).</li>
</ul>
<p>These uses of presence simplify the task of developing compliant clients (cf. &xep0134;).</p>
<p class='box'>It is strongly NOT RECOMMENDED to use directed presence with Entity Capabilities data that differs from the data included in broadcast presence for the purpose of establishing implicit PEP subscriptions to another entity, because the directed presence information will be overwritten by any subsequent presence broadcast.</p>
</section2>
<section2 topic='Filtered Notifications' anchor='approach-filter'>
<p>By default, the existence of an XMPP presence subscription is used to establish a PEP subscription to the account owner's personal eventing data. In order to filter which notifications are sent by the PEP service, the contact's client includes extended &xep0115; information in the presence notifications it sends to the account owner. Because the PEP service supports the "filtered-notifications" feature, it sends only those notifications that match the contact's expressed notification preferences.</p>