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

* doc/guide.tex: Describe in mod_muc: nick register and service admin message (EJAB-400).

Browse Source 
SVN Revision: 981
This commit is contained in:
Badlop 2007-11-26 10:23:37 +00:00
parent 9a03e5087e
commit 731e9cc0e5
2 changed files with 20 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
ChangeLog
View File

@ -1,5 +1,7 @@
2007-11-26 Badlop <badlop@process-one.net>
* doc/guide.tex: Describe in mod_muc: nick register and service admin message (EJAB-400).
* src/mod_echo.erl: Example function that demonstrates how to receive XMPP packets using Erlang's message passing mechanism (EJAB-247).
* src/ejabberdctl.template: Removed bashisms (EJAB-399). Set environment variables instead of passing parameters when calling erl (EJAB-421). Write erl_crash.dump in the log/ directory, with unique filename (EJAB-433).

29
doc/guide.tex
View File

@ -2104,9 +2104,7 @@ Options:
\ind{modules!\modmuc{}}\ind{protocols!XEP-0045: Multi-User Chat}\ind{conferencing}
With this module enabled, your server will support Multi-User Chat
(\xepref{0045}). End users will be able to join text conferences. Notice
that this module is not (yet) clusterable.
(\xepref{0045}). End users will be able to join text conferences.
Some of the features of Multi-User Chat:
\begin{itemize}
@ -2117,6 +2115,23 @@ Some of the features of Multi-User Chat:
\item Kicking and banning participants.
\end{itemize}
The MUC service allows any Jabber ID to register a nickname,
so nobody else can use that nickname in any room in the MUC service.
To register a nickname, open the Service Discovery in your
Jabber client and Register in the MUC service.
The MUC service allows the service administrator to send a message
to all existing chatrooms.
To do so, send the message to the Jabber ID of the MUC service.
This module 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 node managing a
set of rooms goes down, the rooms disappear and they will be recreated
on an available node on first connection attempt.
Options:
\begin{description}
\hostitem{conference}
@ -2286,14 +2301,6 @@ defined, but some user restriction could be added as well:
\end{verbatim}
\end{itemize}
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 node managing a
set of rooms goes down, the rooms disappear and they will be recreated
on an available node on first connection attempt.
\subsection{\modmuclog{}}
\label{modmuclog}
\ind{modules!\modmuclog{}}