Project: ejabberd

Revision: 1563

Author: badlop

Date: 15 Sep 2008 14:38:52

• /trunk/doc/guide.tex

  ......	@@ -750,7 +750,7 @@
  750	750	Handles incoming s2s connections.\\
  751	751	Options: \texttt{inet6}, \texttt{ip}, \texttt{max\_stanza\_size}
  752	752	\titem{\texttt{ejabberd\_service}}
  753		Interacts with \footahref{http://www.ejabberd.im/tutorials-transports}{external components}
  	753	Interacts with an \footahref{http://www.ejabberd.im/tutorials-transports}{external component}
  754	754	(as defined in the Jabber Component Protocol (\xepref{0114}).\\
  755	755	Options: \texttt{access}, \texttt{hosts}, \texttt{inet6},
  756	756	\texttt{ip}, \texttt{shaper}, \texttt{service\_check\_from}
  ......	@@ -772,9 +772,10 @@
  772	772	external components. The option can be either \term{true} or
  773	773	\term{false}. The default value is \term{true} which conforms to \xepref{0114}.
  774	774	\titem{\{hosts, [Hostnames], [HostOptions]\}} \ind{options!hosts}
  775		This option of \term{ejabberd\_service} allows to define one or more hostnames
  776		of external Jabber components that provide a service.
  777		In \term{HostOptions} it is possible to define the password required to those components
  	775	The external Jabber component that connects to this \term{ejabberd\_service}
  	776	can serve one or more hostnames.
  	777	In \term{HostOptions} you can define options for the component;
  	778	currently the only allowed option is the password required to the component
  778	779	when attempt to connect to ejabberd: \poption{\{password, Secret\}}.
  779	780	Note that you cannot define in a single \term{ejabberd\_service} components of
  780	781	different services: add an \term{ejabberd\_service} for each service,
  ......	@@ -2678,7 +2679,9 @@
  2678	2679	status text in presence updates. If disallowed, the \term{status}
  2679	2680	text is stripped before broadcasting the presence update to all
  2680	2681	the room occupants.
  2681		\titem{\{anonymous, true\}} Occupants are allowed to see the real JIDs of other occupants.
  	2682	\titem{\{anonymous, true\}} The room is anonymous:
  	2683	occupants don't see the real JIDs of other occupants.
  	2684	Note that the room moderators can always see the real JIDs of the occupants.
  2682	2685	\titem{\{logging, false\}} The public messages are logged using \term{mod\_muc\_log}.
  2683	2686	\titem{\{max\_users, 200\}} Maximum number of occupants in the room.
  2684	2687	\titem{\{members\_by\_default, true\}} The occupants that enter the room are participants by default, so they have 'voice'.
  ......	@@ -4108,6 +4111,7 @@
  4108	4111
  4109	4112	\begin{verbatim}
  4110	4113	erl -sname ejabberd \
  	4114	-mnesia dir "/var/lib/ejabberd/" \
  4111	4115	-mnesia extra_db_nodes "['ejabberd@first']" \
  4112	4116	-s mnesia
  4113	4117	\end{verbatim}
  ......	@@ -4116,6 +4120,11 @@
  4116	4120	You can check this by running the command `\verb|mnesia:info().|'. You
  4117	4121	should see a lot of remote tables and a line like the following:
  4118	4122
  	4123	Note: the Mnesia directory may be different in your system.
  	4124	To know where does ejabberd expect Mnesia to be installed by default,
  	4125	call \ref{ejabberdctl} without options and it will show some help,
  	4126	including the Mnesia database spool dir.
  	4127
  4119	4128	\begin{verbatim}
  4120	4129	running db nodes = [ejabberd@first, ejabberd@second]
  4121	4130	\end{verbatim}

• /trunk/ChangeLog

  ......	@@ -1,3 +1,10 @@
  	1	2008-09-15 Badlop <badlop@process-one.net>
  	2
  	3	* doc/guide.tex: Fix explanation of mod_muc's anonymous
  	4	option. Make clear that an ejabberd_service can only serve a
  	5	single external component. Provide Mnesia directory when setting
  	6	clustering (thanks to Matthew Reilly)
  	7
  1	8	2008-09-12 Badlop <badlop@process-one.net>
  2	9
  3	10	* src/web/ejabberd_http.hrl: Provide Host, Port, Headers and