moparisthebest
/
xeps
mirror of https://github.com/moparisthebest/xeps
1
0
Fork 0
Code Issues Releases Wiki Activity

clarifications from Christophe Romain 

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@1486 4b5297f7-1745-476d-ba37-a9c6900126ab
This commit is contained in:
Peter Saint-Andre 2007-12-20 18:05:18 +00:00
parent 8d3c1e1f25
commit edd9102bd7
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
xep-0060.xml
View File

@ -5489,7 +5489,7 @@ And by opposing end them?
<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 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 an authorized subscriber to the node (explicitly via subscription or implicitly based on a role of owner or publisher); when the publisher sends a publish request, the service sends the currently published item to the entity (subject to presence checks and notification filtering if appropriate).</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>
@ -7253,7 +7253,7 @@ xmpp:pubsub.shakespeare.lit?pubsub;action=unsubscribe;node=princely_musings
</section1>
<section1 topic='Acknowledgements' anchor='ack'>
<p>Thanks to Gaston Dombiak, Chris Teegarden, Matt Tucker, and Bob Wyman for their feedback.</p>
<p>Thanks to Gaston Dombiak, Christophe Romain, Chris Teegarden, Matt Tucker, and Bob Wyman for their feedback.</p>
</section1>
<section1 topic='Author Note' anchor='authornote'>

2
xep-0163.xml
View File

@ -321,7 +321,7 @@
<li>The default access model is "presence".</li>
<li>A contact's subscription to an account owner's personal eventing data is automatically created because the contact has an XMPP presence subscription (the "auto-subscribe" feature).</li>
<li>Services take account of subscriber presence in the generation of notifications. <note>This works only if the subscription state is "both" (see <cite>RFC 3921</cite>).</note></li>
<li>A service automatically sends notifications to all of the account owner's connected resources.</li>
<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>
</section2>