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
59
|
<!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.2</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.2" target="cvs_checkout" onClick="window.open('/cvs/cvsweb.cgi/~checkout~/code/nelns/doc/server.dxt?rev=1.2','cvs_checkout','resizeable,scrollbars');"><b>download</b></A>)<BR>
Revision <B>1.2</B>, <i>Thu Oct 25 15:00:36 2001 UTC</i> (7 months, 3 weeks ago) by <i>lecroart</i>
<BR>Branch: <b>MAIN</b>
<BR>CVS Tags: <b>HEAD</b><BR>Changes since <b>1.1: +22 -22
lines</b><PRE>
UPDATED
</PRE>
</td></tr></table><HR noshade><PRE>/**
\mainpage NeLNS (Nevrax Library Network Services)
\date 10/25/2001
\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.
- admin_executor_service -> control services on the server (admin_executor_service.cpp)
- admin_service -> control a shard (admin_service.cpp)
- naming_service -> used to find a specific service by its name or service id (naming_service.cpp)
- login_service -> centralized user account manager for all shards (login_service.cpp)
- welcome_service -> translator between login_service and front end of the shard (login_service.cpp)
\subsection nelns_config_files Configuration files
If needing the config file have the extention .cfg and have the same name as the exectuable name (ex: admin_service configuration file name is "admin_service.cfg")
All services inside of the shard must have NSHost and NSPort variable in the config to connect to the naming_service.
For example welcome_service.cfg must have at least:
\code
NSHost = "hostname_of_your_machine_where_naming_service_will_run";
NSPort = 50000;
\endcode
The welcome_service config must also contain the host address of the login_service
\code
LSHost = "hostname_of_your_machine_where_login_service_will_run";
\endcode
\subsection nelns_output_files Output files
The services create/modify the following config or log files:
- log.log (very big especially if you have compiled the services with NL_DEBUG defined) : Contains all debug information sent by the services.
- login_service_database.cfg (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>
|
