This wiki is archived and useful information is being migrated to the main bzflag.org website
Difference between revisions of "Services Proposal"
From BZFlagWiki
(→Proposed features) |
(Moved up Redundancy point, global regristration necessary bit down) |
||
Line 7: | Line 7: | ||
=== Minimum Requirements === | === Minimum Requirements === | ||
The BZFlag global service requires the following minimum features (and example): | The BZFlag global service requires the following minimum features (and example): | ||
− | * | + | * Redundancy or distributed system for minimal failure (geographical distribution) |
* Internal authentication system common to all services | * Internal authentication system common to all services | ||
* Ability to list servers | * Ability to list servers | ||
** Player tracking (Who is where) | ** Player tracking (Who is where) | ||
− | |||
** Players on the server | ** Players on the server | ||
** Team sizes (max and current) | ** Team sizes (max and current) | ||
Line 23: | Line 22: | ||
=== Proposed features === | === Proposed features === | ||
− | |||
* Encrypted logins (by the BZFlag client and/or weblogin) | * Encrypted logins (by the BZFlag client and/or weblogin) | ||
* Registration in the client | * Registration in the client | ||
* Server Push for stats with replication of current data to an API query page for external sites | * Server Push for stats with replication of current data to an API query page for external sites | ||
* Anon usage profile data storage from clients for devs. | * Anon usage profile data storage from clients for devs. | ||
+ | * Knowing if the server requests global auth or not (reg bit to tell people to reg) | ||
+ | * Global group management | ||
=== Considerations === | === Considerations === |
Revision as of 00:37, 31 March 2008
This is a proposal for a revamped BZFlag services system (list server, BZFlag forum, and website) by AAA. Post comments on the Discussion page
Contents
Features
Minimum Requirements
The BZFlag global service requires the following minimum features (and example):
- Redundancy or distributed system for minimal failure (geographical distribution)
- Internal authentication system common to all services
- Ability to list servers
- Player tracking (Who is where)
- Players on the server
- Team sizes (max and current)
- Custom server status info (Game timer, game status)
- Restricting server visibility by global group (advertise)
- Get org names from the group manager for client sorting
- Forum with common authentication
- Wiki with common authentication
- Token store with common authentication, for authenticating users to 3rd parties
- Backwards compatibility in some way with 1.10.x and 2.0.x
Proposed features
- Encrypted logins (by the BZFlag client and/or weblogin)
- Registration in the client
- Server Push for stats with replication of current data to an API query page for external sites
- Anon usage profile data storage from clients for devs.
- Knowing if the server requests global auth or not (reg bit to tell people to reg)
- Global group management
Considerations
- Lightweight where possible
Other services
- Image/texture uploading and hosting