WORD OF WARNING:
================
 - Allways keep the network_settings.conf file from the data repos up-to-date!! Its very important, that the user numbers are synchronized!


WORKING_STACK:
==============
 - removed compiler warnings in some modules
 - totaly rework of the permission system
 - introduced a new PERMISSION layer: PERMISSION_SERVER which gives the nearest server the authority to handle


UNSOLVED:
=========
 - the clients cant get its ip in the handleHandshakes without throwing sigseg
 - MessageManager: proxy/server forward the messages always. Perhaps there is a case, where messages get forwarded forever if there is a loop in the network. think about it again.
 - Permissions: Proxy Servers shouldn't be able to create new eneitites on the server
 - the nick name must be handled new



This readme just gives some hints for the general network programming:

ARCHITECTURE:
The NetworkStream is in the center of this structure.


UserId:
=======
containing the id of a user (==client). This id must be unique within a orxonox network its used especialy in the NetworkStream for node identification and also in the Synchronizeable base class for permissions checking (PERMISSION_OWNER)

the connections belonging tu toe userId's are stored in the NetworkStream::peers std::map. As a keyvalue the userId's are used. Therefore the usage of this peers map is very delicate. Don't ever try to add anything you are not sure about the id stuff.

There are some reserved id's, don't mess with them:
0 :                  Master Server
1 :                  First Proxy Server
2 :                  Second Proxy Server
3 :                  Third Proxy Server
4 :                  Fourth Proxy Server
.
.
.
NET_MAX_PROXY        The maximal number of proxy servers
NET_MAX... + 1       First Client
NET_MAX... + 2       Second Client
.
.
.
NET_MAX_CONNECTION   Last client

The proxy server ids are assigned as stated in the data/trunk/config/network_settings.conf, the first proxy server in the list gets the id NET_ID_PROXY_01 and so on.


The ids are created by the master/proxy servers. Each server receives an address space of 1000 nodes where it is able to assign nodes to. This address space could be extended quite easely, since we got plenty of numbers in 4bytes (integer)

The handshake sync has always the uniqueId == userId. This is why there are some reserved uniqueIds


uniqueId:
=========
uniqueId is an id (unique :D) for each synchronizeable to be identified in a network. the number space for uniqueIds goes from 0 to maxplayers - 1

The handshake sync has always the uniqueId == userId. This is why there are some reserved uniqueIds


permissions:
============
Each synchronizeable variable has some write permissions. this permission systems allows to manage which network nodes are able to write the variables.
PERMISSION_MASTER_SERVER       : only the master server can write this variable
PERMISSION_PROXY_SERVER        : only the proxy server can write this variable
PERMISSION_OWNER               : only the owner can write this variable
PERMISSION_ALL                 : all clients can write this variable

Only the master server should have the permission to create new WorldEntities and to add them to the game




NetworkStream PeerInfo list: (peers)
=====================================
The network node with the offset 0 is always the server to which the client must connect to (in case there are connections to other hosts at the same time).



MessageManager:
===============
The message manager has special handling if its a master/proxy: the messages will simply be forwarded to the other server


Proxy Control:
==============
The ProxyControl class manages the state of the network by exchanging state messages.