moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-21 16:55:07 -05:00
Code Issues Releases Wiki Activity

further trigger clarifications

Browse Source 
git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1217 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2007-09-14 17:29:18 +00:00
parent c7454d8b94
commit 4a603d79d6
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
xep-0060.xml
View File

@ -5333,10 +5333,10 @@ And by opposing end them?
<section2 topic='Notification Triggers' anchor='impl-notify'>
<p>There are many possible triggers for sending a notification to an entity for the currently published item or the last published item, as summarized below:</p>
<ol>
<li>The entity has explicitly requested one or more items from the node and is authorized to retrieve items.</li>
<li>The entity is an authorized subscriber to the node; The publisher sends a publish request, the service sends the currently published item to the entity.</li>
<li>The entity is not subscribed but is eligible to do so and has sent presence (potentially containing appropriate entity capabilities data) to a node that is presence-enabled; when the publisher sends a publish request, the service sends the currently published item to the entity.</li>
<li>The entity is not subscribed but is eligible to do so and sends presence (potentially containing appropriate entity capabilities data) to a node that is presence-enabled; as a result, the service sends the last published item to the entity.</li>
<li>The entity explicitly requests one or more items from the node and is authorized to retrieve items; when the service receives such a request, it sends the items to the entity.</li>
<li>The entity is an authorized subscriber to the node; when the publisher sends a publish request, the service sends the currently published item to the entity.</li>
<li>The entity is not subscribed but is eligible to do so and sends presence containing appropriate entity capabilities data to a service that supports filtered notifications (effectively establishing a "temporary subscription"); when the service receives such presence, it sends the last published item to the entity.</li>
<li>The entity is not subscribed but is eligible to do so and has sent presence containing appropriate entity capabilities data to a service that supports filtered notifications (effectively establishing a "temporary subscription"); when the publisher sends a publish request that matches the entity's expressed notification interests, the service sends the currently published item to the entity.</li>
<li>The entity gains access to the node because of a change to the node access model; as a result, the service sends the last published item to the entity.</li>
<li>The entity is added to the roster group associated with a node access model of "roster"; as a result, the service sends the last published item to the entity.</li>
</ol>