Project

General

Profile

Server » History » Version 2

Andreas Schneider, 04/12/2009 03:38 PM

1 1 Andreas Schneider
h1. Server
2
3 2 Andreas Schneider
CentrED is built on the client-server architecture. This means, that there are two seperate programs involved: the Client and the Server. Both [[Protocol|communicate]] over a network via "TCP":http://en.wikipedia.org/wiki/Transmission_Control_Protocol.
4 1 Andreas Schneider
The Client displays the map to the user and offers several tools to modify it as well as to control the server. The Server on the other hand takes these requests, processes them and shares them between all connected clients.
5 2 Andreas Schneider
6
h2. Requirements
7
8
The CentrED server is a command line application. This means that you should be able to handle the command line shell of the Operating System you use. Apart from that, you should also prepare for the following:
9
* i386 Windows or Linux (although it should run fine in 64bit versions too)
10
* at least 100MB of RAM
11
* an open port on your machine and if necessary the ability to forward ports
12
13
h2. Configuration
14
15
The server looks for a config file with the same name as the server itself but the extension ".ini". In the default distribution, this file should be called "cedserver.ini".
16
17
Before you can start the server, such a file has to be created. On win32, the server will automatically query all necessary values on startup, if no such config file is found. On Linux however, you have to start the server with the parameter "--init".
18
19
You will then encounter a screen similar to this:
20
<pre>
21
Configuring Network
22
===================
23
Port [2597]: _
24
</pre>
25
This means, that the server expects your input for which port to use. If you enter nothing and just press [Enter], the default value as indicated by the brackets "2597" will be used.
26
27
h2. Startup
28
29
The server is started by simply invoking _cedserver_ from the commandline. Make sure that the specified port as well as the referenced map files are not in use by other programs. The map is loaded with *exclusive* read/write permissions which means, that no other program can access them at the same time. This is not the case for radarcol.mul and tiledata.mul, since these are loaded read-only.