mirror of
https://github.com/moparisthebest/xeps
synced 2024-08-13 16:53:48 -04:00
Better wording and attempt to prepare revision notes
This commit is contained in:
parent
ea1f090ed3
commit
df0f08bf1d
41
xep-0033.xml
41
xep-0033.xml
@ -26,6 +26,13 @@
|
|||||||
&hildjj;
|
&hildjj;
|
||||||
&stpeter;
|
&stpeter;
|
||||||
|
|
||||||
|
<revision>
|
||||||
|
<version>1.2</version>
|
||||||
|
<date>2015-09-22</date>
|
||||||
|
<initials>mre</initials>
|
||||||
|
<remark>Clarification: Multicast service MUST track directed presence broadcast to later ensure broadcast of subsequent unvailable presence to the same receiving parties.</remark>
|
||||||
|
</revision>
|
||||||
|
|
||||||
<revision>
|
<revision>
|
||||||
<version>1.1</version>
|
<version>1.1</version>
|
||||||
<date>2004-09-15</date>
|
<date>2004-09-15</date>
|
||||||
@ -287,18 +294,28 @@
|
|||||||
<section1 topic='Business Rules' anchor='rules'>
|
<section1 topic='Business Rules' anchor='rules'>
|
||||||
<section2 topic='Directed Presence' anchor='presence'>
|
<section2 topic='Directed Presence' anchor='presence'>
|
||||||
|
|
||||||
<p>The multicast service MUST keep track of the entities it
|
<p>This specification can be used to, in effect, send directed
|
||||||
sent a presence with an absent 'type' attribute (i.e. an
|
presence (see Section 4.6 of &rfc6121;). In order to ensure
|
||||||
'available' presence) to and the originating entity of that
|
that entities that have received directed available presence
|
||||||
presence. If the multicast service receives an unavailable
|
through the service also are informed when the originating
|
||||||
presence from one of the tracked originating entities, it MUST
|
entity sends unavailable presence, the multicast service MUST
|
||||||
broadcast this presence to all tracked entities which have not
|
do the following:</p>
|
||||||
yet received an unavailable presence from the originating
|
|
||||||
entity, even if the presence does not contain explicit
|
|
||||||
broadcast addresses. Thus the multicast service ensures that
|
<ol>
|
||||||
all entities, which have received an (directed) 'available'
|
<li>Keep track of the entities to which it sends available
|
||||||
presence over it, receive the related 'unavailable'
|
presence (i.e., presence stanzas with no 'type' attribute)
|
||||||
presence.</p>
|
along with the originating entity of that presence.</li>
|
||||||
|
|
||||||
|
<li>Upon receiving a presence stanza of type "unavailable"
|
||||||
|
from an originating entity, broadcast that unavailable
|
||||||
|
presence to all entities to which it has send available
|
||||||
|
presence.</li>
|
||||||
|
</ol>
|
||||||
|
|
||||||
|
<p>In this way, the multicast service ensures that all
|
||||||
|
entities which have received available presence through the
|
||||||
|
service also receive the associated unavailable presence.</p>
|
||||||
</section2>
|
</section2>
|
||||||
</section1>
|
</section1>
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user