moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-22 09:12:19 -05:00
Code Issues Releases Wiki Activity

Fixing namespace consistence in FMR

Browse Source
This commit is contained in:
Kevin Smith 2012-01-10 17:15:42 +00:00
parent f7a02f86c1
commit eb4e82b78d
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
inbox/fastmuc.xml
View File

@ -37,7 +37,7 @@ Appropriate action - alert user, attempt to rejoin MUC, whatever.
</section1> </section1>
<section1 topic='Discovery' anchor='discovery'> <section1 topic='Discovery' anchor='discovery'>
<p>MUC Rooms supporting this should have a disco feature of "urn:xmpp:mfr" in caps.</p> <p>MUC Rooms supporting this should have a disco feature of "urn:xmpp:presence-session:0" in caps.</p>
<p>To avoid extra roundtrips for discovery, clients may speculatively send elements when initially joining a MUC, and treat the absense of appropriate elements in the responses to indicate a lack of support.</p> <p>To avoid extra roundtrips for discovery, clients may speculatively send elements when initially joining a MUC, and treat the absense of appropriate elements in the responses to indicate a lack of support.</p>
</section1> </section1>
@ -49,7 +49,7 @@ Appropriate action - alert user, attempt to rejoin MUC, whatever.
from='romeo@montague.lit/lane' from='romeo@montague.lit/lane'
to='orchard@chat.capulet.lit/Romeo'> to='orchard@chat.capulet.lit/Romeo'>
<x xmlns='http://jabber.org/protocol/muc'/> <x xmlns='http://jabber.org/protocol/muc'/>
<presence-session xmlns="urn:xmpp:pressence-session:0"/> <presence-session xmlns="urn:xmpp:presence-session:0"/>
</presence> </presence>
]]></example> ]]></example>
<p>If a client has indicated that it's using MUC Fast Reconnect on its session, the MUC service MUST annotate the presence stanzas it sends with elements containing a presence-session element with namespace "urn:xmpp:presence-session:0", a "session" attribute and an "id" attribute, described below.</p> <p>If a client has indicated that it's using MUC Fast Reconnect on its session, the MUC service MUST annotate the presence stanzas it sends with elements containing a presence-session element with namespace "urn:xmpp:presence-session:0", a "session" attribute and an "id" attribute, described below.</p>
@ -60,7 +60,7 @@ Appropriate action - alert user, attempt to rejoin MUC, whatever.
<x xmlns='http://jabber.org/protocol/muc#user'> <x xmlns='http://jabber.org/protocol/muc#user'>
<item affiliation='owner' role='moderator'/> <item affiliation='owner' role='moderator'/>
</x> </x>
<presence-session xmlns="urn:xmpp:pressence-session:0" session="u8e8t2thu" id="893oehh"/> <presence-session xmlns="urn:xmpp:presence-session:0" session="u8e8t2thu" id="893oehh"/>
</presence> </presence>
]]></example> ]]></example>
<p>Attributes:</p> <p>Attributes:</p>
@ -76,7 +76,7 @@ Appropriate action - alert user, attempt to rejoin MUC, whatever.
from='romeo@montague.lit/lane' from='romeo@montague.lit/lane'
to='orchard@chat.capulet.lit/Romeo'> to='orchard@chat.capulet.lit/Romeo'>
<x xmlns='http://jabber.org/protocol/muc'/> <x xmlns='http://jabber.org/protocol/muc'/>
<presence-session-resume xmlns="urn:xmpp:pressence-session:0" session="u8e8t2thu" id="893oehh"/> <presence-session-resume xmlns="urn:xmpp:presence-session:0" session="u8e8t2thu" id="893oehh"/>
</presence> </presence>
]]></example> ]]></example>
<p>When the MUC room receives a room fast rejoin request, it must either first send an 'unavailable' presence from the room's bare JID, followed by a normal full join, as above, or instead of sending the full presence list for all occupants, only send those stanzas needed to get from the state represented by the client-provided session and id to the current state. All the presence stanzas (apart from the unavailable one used to reset state before a clean join) MUST contain the presence-session element as described above.</p> <p>When the MUC room receives a room fast rejoin request, it must either first send an 'unavailable' presence from the room's bare JID, followed by a normal full join, as above, or instead of sending the full presence list for all occupants, only send those stanzas needed to get from the state represented by the client-provided session and id to the current state. All the presence stanzas (apart from the unavailable one used to reset state before a clean join) MUST contain the presence-session element as described above.</p>