1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML>
<HEAD><style> A { color:black }</style>
<!-- hennerik CVSweb $Revision: 1.93 $ -->
<TITLE>code/nelns/doc/server.dxt - view - 1.1</TITLE></HEAD>
<BODY BGCOLOR="#eeeeee">
<table width="100%" border=0 cellspacing=0 cellpadding=1 bgcolor="#aaaaaa"><tr valign=bottom><td><a href="server.dxt"><IMG SRC="/inc/img/picto-up.gif" ALT="[BACK]" BORDER="0" WIDTH="14" HEIGHT="13"></a> <b>Return to <A HREF="server.dxt">server.dxt</A>
CVS log</b> <IMG SRC="/inc/img/picto-news.gif" ALT="[TXT]" BORDER="0" WIDTH="13" HEIGHT="15"></td><td align=right><IMG SRC="/inc/img/picto-dir.gif" ALT="[DIR]" BORDER="0" WIDTH="15" HEIGHT="13"> <b>Up to <a href="/cvs/cvsweb.cgi/">Nevrax</a> / <a href="/cvs/cvsweb.cgi/code/">code</a> / <a href="/cvs/cvsweb.cgi/code/nelns/">nelns</a> / <a href="/cvs/cvsweb.cgi/code/nelns/doc/">doc</a></b></td></tr></table><HR noshade><table width="100%"><tr><td bgcolor="#ffffff">File: <a href="/cvs/cvsweb.cgi/">Nevrax</a> / <a href="/cvs/cvsweb.cgi/code/">code</a> / <a href="/cvs/cvsweb.cgi/code/nelns/">nelns</a> / <a href="/cvs/cvsweb.cgi/code/nelns/doc/">doc</a> / <a href="/cvs/cvsweb.cgi/code/nelns/doc/server.dxt">server.dxt</a> (<A HREF="/cvs/cvsweb.cgi/~checkout~/code/nelns/doc/server.dxt?rev=1.1" target="cvs_checkout" onClick="window.open('/cvs/cvsweb.cgi/~checkout~/code/nelns/doc/server.dxt?rev=1.1','cvs_checkout','resizeable,scrollbars');"><b>download</b></A>)<BR>
Revision <B>1.1</B>, <i>Wed Apr 18 13:54:25 2001 UTC</i> (15 months, 1 week ago) by <i>valignat</i>
<BR>Branch: <b>MAIN</b>
<PRE>
RENAMED code/server to code/nelns.
</PRE>
</td></tr></table><HR noshade><PRE>/**
\mainpage Server
\section server_intro Introduction
This documentation describes NEVRAX NeL Network Services, a set of services built on the top of NeL. One service is usually one process. A service class must be or inherit from NLNET::IService. Report to NeL documents for further information.
The format of the messages that can be processed by a service are described in the documentation of the .cpp file of the service, in the detailed description of the callbacks. For example, if you want to know how to interact with the Naming Service (or rather how NLNET::CNamingClient interacts with it), read the documentation of naming_service.cpp.
\subsection nelns_services The NEVRAX NeL Network Services
NeLNS is made up of one unique login service, one or several shards (aka game servers), and a few utility services.
- naming_service -> used to find a specific service by its name (naming_service.cpp)
- log_service -> centralized logger for all services (log_service.cpp)
- time_service -> centralized time reference manager (time_service.cpp)
- login_service -> centralized user account manager for all shards (login_service.cpp)
- admin_executor_service -> collects stats about a physical machine (admin_executor_service.cpp)
- agent_service -> routes messages for inter-agent communication over several machines (agent_service.cpp)
\subsection nelns_config_files Configuration files
For all services : ns.cfg
\code
Host = "hostname_of_your_machine_where_naming_service_will_run";
Port = 50000;
\endcode
For login_service : ls.txt
\code
Shards = {
"hostname_of_your_machine_where_game_service_will_run", "Name of the shard as it will appear on the client"
};
\endcode
\subsection nelns_output_files Output files
The services create/modify the following config or log files:
- unitime.cfg (time_service) : Contains the time reference
- logs.log (very big especially if you have compiled the services with NL_DEBUG defined) (log_service) : Contains all debug information sent by the services.
- ls.txt (login_service) : Every time a new user (not registered before) logs in, its login
and password are saved into ls.txt
- ls.log (login_service) : Every time someone logs in, its configuration information is
saved into ls.log
*/
</PRE>
|
