Generic Server Application
[Stechec]

Collaboration diagram for Generic Server Application:

Located in stechec/server directory. More...

Classes
class	ClientStatistic
	Clients statistics that can be retrieved from Client. Originated from a kludge: Generic server and arbiter have several different informations on each client. They are all grouped here (with the CoachErrorCustom rules class), then resend to rules at the end so it can write stats, calculate scores, ... More...
class	server::Client
	Keep additional data about a client (statistics, status, ...). More...
class	server::GameHosting
	Represents a game, with up to two coachs and as many viewers as they could be. Each game is identified by a uid, passed to the ctor. More...
class	server::Server
	Control multiple game, receive new clients, handle spectators... More...
Defines
#define	MAX_CONNECTION   250
	Maximum number of coachs + spectators connected on server.
Enumerations
enum	server::eGameState {   server::eStarting = 0, server::eWaiting, server::ePlaying, server::eFinishing,   server::eFinished, server::eCrashed }
	Status of a single server game thread. More...

---

Detailed Description

Located in stechec/server directory.

---

Enumeration Type Documentation

enum server::eGameState

Status of a single server game thread.

Enumerator:

eStarting	Starting thread.
eWaiting	Wait for players.
ePlaying	Game playing.
eFinishing	Game finished. Wait for last clients to exit.
eFinished	Thread can be cleaned.
eCrashed	Thread can be cleaned, but it was termined anormally.

---