From 1834fb3a724365d804f5c863a27b720ac9bf45b9 Mon Sep 17 00:00:00 2001 From: Alexey Shchepin Date: Mon, 14 Jul 2003 18:06:03 +0000 Subject: * src/ejabberd_s2s_out.erl: Close connection after key verification * src/ejabberd_c2s.erl: start replaced with start_link * src/ejabberd_s2s_in.erl: Likewise * src/ejabberd_s2s_out.erl: Likewise * src/ejabberd_service.erl: Likewise * src/ejabberd_listener.erl: Now uses proc_lib to spawn listeners, removed 3rd parameter in listener configuration (assumed to equal start_link) * src/ejabberd.rel: Updated * doc/guide.tex: Small changes * doc/Makefile: Added implicit charset specification to hevea SVN Revision: 124 --- doc/guide.tex | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc/guide.tex') diff --git a/doc/guide.tex b/doc/guide.tex index 0142437d4..0c0a6d0fe 100644 --- a/doc/guide.tex +++ b/doc/guide.tex @@ -64,9 +64,9 @@ The main features of \ejabberd{} is: \begin{itemize} \item Works on most of popular platforms: *nix (tested on Linux and FreeBSD) and Win32 -\item Distributed: You may run \ejabberd{} on a cluster of machines and all of +\item Distributed: You can run \ejabberd{} on a cluster of machines and all of them will serve one Jabber domain. -\item Fault-tolerance: You may setup an \ejabberd{} cluster so that all the +\item Fault-tolerance: You can setup an \ejabberd{} cluster so that all the information required for a properly working service will be stored permanently on more than one node. This means that if one of the nodes crashes, then the others will continue working without disruption. -- cgit v1.2.3