Services Proposal

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

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 if the server requests global auth or not (reg bit to tell people to reg)
  • 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

• Redunancy or Distributed nature for speed and relyability
• Encrypted logins (by the BZFlag client and/or weblogin)
• Registration in the client

Considerations

• Lightweight where possible

Other services

• Image/texture uploading and hosting