Chapril/xmpp.chapril.org-ejabberd
25
1
Fork 0
mirror of https://github.com/processone/ejabberd.git synced 2024-11-28 16:34:13 +01:00
Code Releases Activity

* doc/guide.tex: Typos

Browse Source 
SVN Revision: 795
This commit is contained in:
Mickaël Rémond 2007-06-25 17:44:48 +00:00
parent 20da906311
commit 6c3a79f9df
2 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
ChangeLog
View File

@ -1,5 +1,7 @@
2007-06-25 Mickael Remond <mickael.remond@process-one.net> 2007-06-25 Mickael Remond <mickael.remond@process-one.net>
* doc/guide.tex: Typos
* src/mod_muc/mod_muc_room.erl: New anti-abuse options: * src/mod_muc/mod_muc_room.erl: New anti-abuse options:
min_presence_interval and min_message_interval min_presence_interval and min_message_interval
* doc/guide.tex: Likewise * doc/guide.tex: Likewise

4
doc/guide.tex
View File

@ -1949,7 +1949,7 @@ describing the reason why the message is not acceptable.
This option defines the minimum of time between presence changes This option defines the minimum of time between presence changes
coming from a given user in seconds. This option is global and valid coming from a given user in seconds. This option is global and valid
for all chat rooms. A decimal value can be used. When this option is for all chat rooms. A decimal value can be used. When this option is
not defined, no restriction are applied. This option can be used to not defined, no restriction is applied. This option can be used to
protect a MUC service for users abuses, as fastly changing a user protect a MUC service for users abuses, as fastly changing a user
presence will result in possible large presence packet broadcast. If a presence will result in possible large presence packet broadcast. If a
user tries to change its presence more often than the specified user tries to change its presence more often than the specified
@ -2039,7 +2039,7 @@ The Multi-Users Chat module now supports clustering and load
balancing. One module can be started per cluster node. Rooms are balancing. One module can be started per cluster node. Rooms are
distributed at creation time on all available MUC module distributed at creation time on all available MUC module
instances. The multi-user chat module is clustered but the room instances. The multi-user chat module is clustered but the room
themselves are not clustered nor fault-tolerant: If the not managing a themselves are not clustered nor fault-tolerant: If the node managing a
set of rooms goes down, the rooms disappear and they will be recreated set of rooms goes down, the rooms disappear and they will be recreated
on an available node on first connection attempt. on an available node on first connection attempt.