This wiki is archived and useful information is being migrated to the main bzflag.org website
Difference between revisions of "Services Proposal"
From BZFlagWiki
(Initial import) |
(More details) |
||
| Line 3: | Line 3: | ||
Post comments on the [[Talk:BZFlag_Services_Proposal|Discussion page]] | Post comments on the [[Talk:BZFlag_Services_Proposal|Discussion page]] | ||
| − | == Minimum Requirements == | + | == Features == |
| − | The BZFlag global service | + | |
| + | === Minimum Requirements === | ||
| + | The BZFlag global service requires the following minimum features (and example): | ||
| + | * No single point of 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 | ||
| Line 14: | Line 17: | ||
** Restricting server visibility by global group | ** Restricting server visibility by global group | ||
* Forum with common authentication | * Forum with common authentication | ||
| − | |||
* Wiki with common authentication | * Wiki with common authentication | ||
* Token store with common authentication, for authenticating users to 3rd parties | * Token store with common authentication, for authenticating users to 3rd parties | ||
| − | == 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 | ||
| + | |||
| + | === Considerations === | ||
| + | * Lightweight where possible | ||
| + | |||
| + | === Other services === | ||
| + | * Image/texture uploading and hosting | ||
Revision as of 23:52, 30 March 2008
|
This page contains the design document for an enhancement or feature. It is a work of collaborative development, and may not represent the final design. If you are not part of the development or design group, please post comments and suggestions on the talk page and not in the middle of the design. |
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):
- No single point of failure (geographical distribution)
- Internal authentication system common to all services
- Ability to list servers
- Player tracking (Who is where)
- Knowing minimum requirements to talk, join, and spawn
- Players on the server
- Team sizes (max and current)
- Custom server status info (Game timer, game status)
- Restricting server visibility by global group
- Forum with common authentication
- Wiki with common authentication
- Token store with common authentication, for authenticating users to 3rd parties
Proposed features
- Encrypted logins (by the BZFlag client and/or weblogin)
- Registration in the client
Considerations
- Lightweight where possible
Other services
- Image/texture uploading and hosting
