Difference between revisions of "Match coordinator module"
m (wrong link in blueprint) |
|||
| Line 1: | Line 1: | ||
{{Blueprint|match-coordinator}} | {{Blueprint|match-coordinator}} | ||
| − | |||
| − | == | + | Basically, it's a module to make organized matches or tournaments easier to organize. Anybody could set up a match in 10 minutes. |
| − | + | ||
| + | == Goals and features == | ||
| + | * Basic match organization admin commands | ||
| + | * Automated, or remotely-organized matches, when connected to a Match Coordination Server | ||
== Concept Overview == | == Concept Overview == | ||
| + | There's two entities: the server, and the match coordination server, which we will call MCS. | ||
| + | |||
| + | A server admin is free to choose it's own MCS, either one just for his server, one for some servers, or a big network of servers interconnected trough an MCS. The server will poll the MCS once in a while(TBD) and identify to it(using AAGID) to check for upcoming matches or other useful information, like an arbitrary mesage, eg. the results of another match if we're in a tournament, or to communicate information it gathered(eg. match scores). | ||
| + | |||
| + | == Detailed Concept Points == | ||
| + | === Communication between the server and the MCS === | ||
| + | The communication between these entities will be done trough the '''AA''' '''M'''atch '''C'''oordination '''P'''rotocol(AAMCP), which is defined later in this document0 | ||
== Communication protocols involved == | == Communication protocols involved == | ||
| + | === AAMCP === | ||
| + | Used from [[#Communication_between_the_server_and_the_MCS|here]]. | ||
| + | TBD | ||
| − | == Admin interface == | + | == Admin interface and settings == |
| + | ''This part depends on [[New setting structure]] and [[New admin UI]] and therefore can't be detailed now.'' | ||
Revision as of 07:58, 23 September 2008
Basically, it's a module to make organized matches or tournaments easier to organize. Anybody could set up a match in 10 minutes.
Goals and features
- Basic match organization admin commands
- Automated, or remotely-organized matches, when connected to a Match Coordination Server
Concept Overview
There's two entities: the server, and the match coordination server, which we will call MCS.
A server admin is free to choose it's own MCS, either one just for his server, one for some servers, or a big network of servers interconnected trough an MCS. The server will poll the MCS once in a while(TBD) and identify to it(using AAGID) to check for upcoming matches or other useful information, like an arbitrary mesage, eg. the results of another match if we're in a tournament, or to communicate information it gathered(eg. match scores).
Detailed Concept Points
Communication between the server and the MCS
The communication between these entities will be done trough the AA Match Coordination Protocol(AAMCP), which is defined later in this document0
Communication protocols involved
AAMCP
Used from here. TBD
Admin interface and settings
This part depends on New setting structure and New admin UI and therefore can't be detailed now.
