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

1.25rc10

Browse Source
This commit is contained in:
stpeter 2011-12-20 10:31:59 -07:00
parent fdb9a6f8c0
commit 1b6f49bf6f
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
xep-0045.xml
View File

@ -47,8 +47,8 @@
<registry/> <registry/>
&stpeter; &stpeter;
<revision> <revision>
<version>1.25rc9</version> <version>1.25rc10</version>
<date>in progress, last updated 2011-12-16</date> <date>in progress, last updated 2011-12-20</date>
<initials>psa</initials> <initials>psa</initials>
<remark> <remark>
<ul> <ul>
@ -1569,7 +1569,7 @@
</error> </error>
</presence> </presence>
]]></example> ]]></example>
<p>Alternatively, the room could kick an "idle user" in order to free up space (whether the definition of "idle user" is up to the implementation).</p> <p>Alternatively, the room could kick an "idle user" in order to free up space (where the definition of "idle user" is up to the implementation).</p>
<p>If the room has reached its maximum number of occupants and a room admin or owner attempts to join, the room MUST allow the admin or owner to join, up to some reasonable number of additional occupants; this helps to prevent denial of service attacks caused by stuffing the room with non-admin users.</p> <p>If the room has reached its maximum number of occupants and a room admin or owner attempts to join, the room MUST allow the admin or owner to join, up to some reasonable number of additional occupants; this helps to prevent denial of service attacks caused by stuffing the room with non-admin users.</p>
</section3> </section3>
@ -1754,7 +1754,7 @@
</section3> </section3>
<section3 topic='Room Subject' anchor='enter-subject'> <section3 topic='Room Subject' anchor='enter-subject'>
<p>After the room has optionally sent the discussion history to the new occupant, it SHALL send the current room subject (if any). This is a &MESSAGE; stanza from the room itself (or from the room JID of the entity that set the subject), with a &SUBJECT; element but no &BODY; element, as shown in the following example.</p> <p>After the room has optionally sent the discussion history to the new occupant, it SHALL send the current room subject. This is a &MESSAGE; stanza from the room itself (or from the room JID of the entity that set the subject), with a &SUBJECT; element but no &BODY; element, as shown in the following example.</p>
<example caption='Service Informs New Occupant of Room Subject'><![CDATA[ <example caption='Service Informs New Occupant of Room Subject'><![CDATA[
<message <message
from='coven@chat.shakespeare.lit/secondwitch' from='coven@chat.shakespeare.lit/secondwitch'
@ -1778,7 +1778,7 @@
</section3> </section3>
<section3 topic='Live Messages' anchor='enter-live'> <section3 topic='Live Messages' anchor='enter-live'>
<p>After the room has optionally sent the room subject, it SHALL begin to send live messages, presence changes, occupant "joins" and "leaves", and other real-time traffic ot the new occupant, as described in other sections of this document.</p> <p>After the room has sent the room subject, it SHALL begin to send live messages, presence changes, occupant "joins" and "leaves", and other real-time traffic ot the new occupant, as described in other sections of this document.</p>
</section3> </section3>
<section3 topic='Error Conditions' anchor='enter-errorcodes'> <section3 topic='Error Conditions' anchor='enter-errorcodes'>