diff options
author | Mickaël Rémond <mickael.remond@process-one.net> | 2007-06-25 17:44:48 +0000 |
---|---|---|
committer | Mickaël Rémond <mickael.remond@process-one.net> | 2007-06-25 17:44:48 +0000 |
commit | 6c3a79f9df4f3430fa4289017a0a12995dd1736a (patch) | |
tree | 096ca8de06a216c670bafb097b2633cf953d785a | |
parent | * src/mod_muc/mod_muc_room.erl: New anti-abuse options: min_presence_interval... (diff) |
* doc/guide.tex: Typos
SVN Revision: 795
Diffstat (limited to '')
-rw-r--r-- | ChangeLog | 2 | ||||
-rw-r--r-- | doc/guide.tex | 4 |
2 files changed, 4 insertions, 2 deletions
@@ -1,5 +1,7 @@ 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: min_presence_interval and min_message_interval * doc/guide.tex: Likewise diff --git a/doc/guide.tex b/doc/guide.tex index 4b117ba0..69a62eb4 100644 --- a/doc/guide.tex +++ b/doc/guide.tex @@ -1949,7 +1949,7 @@ describing the reason why the message is not acceptable. This option defines the minimum of time between presence changes 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 -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 presence will result in possible large presence packet broadcast. If a 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 distributed at creation time on all available MUC module 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 on an available node on first connection attempt. |