mirror of
https://github.com/moparisthebest/xeps
synced 2024-12-22 07:38:52 -05:00
Multicast service MUST track directed presence broadcast
This is to ensure entity will not stay permanently seen as online after a multicasted directed presence.
This commit is contained in:
parent
44545f0a08
commit
be6ba8a5ae
19
xep-0033.xml
19
xep-0033.xml
@ -284,6 +284,25 @@
|
||||
</section2>
|
||||
</section1>
|
||||
|
||||
<section1 topic='Business Rules' anchor='rules'>
|
||||
<section2 topic='Directed Presence' anchor='presence'>
|
||||
<p>To ensure that entities that have received directed
|
||||
presence through a multicast service will get the unvailable
|
||||
presence when the originating client closes the its session,
|
||||
the multicast service should also relay unvailable presence
|
||||
stanzas.</p>
|
||||
<p>When transferring an extended addressing presence stanza,
|
||||
the multicast service MUST keep track of the entities that
|
||||
have received the individual directed presence packets.</p>
|
||||
<p>When the multicast service receive an unavailable presence
|
||||
stanza without extended addresses, it MUST broadcast the
|
||||
updated presence to all the entities that have received a
|
||||
directed presence previously (if the multicast service has not
|
||||
yet sent unavailable presence to a precise entity through a
|
||||
previous extended stanza presence).</p>
|
||||
</section2>
|
||||
</section1>
|
||||
|
||||
<section1 topic='Multicast Usage' anchor='multicast'>
|
||||
<p>The following usage scenario shows how messages flow through both address-enabled and non-address-enabled portions of the Jabber network.</p>
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user