Services Proposal - Revision history

AAA: server version

2008-03-31T00:38:47Z

server version

← Older revision		Revision as of 00:38, 31 March 2008
Line 16:		Line 16:
	** Restricting server visibility by global group (advertise)		** Restricting server visibility by global group (advertise)
	** Get org names from the group manager for client sorting		** Get org names from the group manager for client sorting
			** Server version
	* Forum with common authentication		* Forum with common authentication
	* Wiki with common authentication		* Wiki with common authentication

AAA: Moved up Redundancy point, global regristration necessary bit down

2008-03-31T00:37:30Z

Moved up Redundancy point, global regristration necessary bit down

← Older revision		Revision as of 00:37, 31 March 2008
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):
	* ~~No single point of~~ failure (geographical distribution)		* 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)
	** Knowing if the server requests global auth or not (reg bit to tell people to reg)
	** 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 ===
	* Redundancy or Distributed nature for speed and reliability
	* 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 ===

JeffM2501: /* Proposed features */

2008-03-31T00:05:34Z

Proposed features

← Older revision		Revision as of 00:05, 31 March 2008
Line 23:		Line 23:

	=== Proposed features ===		=== Proposed features ===
	* ~~Redunancy~~ or Distributed nature for speed and ~~relyability~~		* Redundancy or Distributed nature for speed and reliability
	* 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
			* Anon usage profile data storage from clients for devs.

	=== Considerations ===		=== Considerations ===

JeffM2501: /* Features */

2008-03-31T00:04:13Z

Features

← Older revision		Revision as of 00:04, 31 March 2008
Line 20:		Line 20:
	* 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
			* Backwards compatibility in some way with 1.10.x and 2.0.x

	=== Proposed features ===		=== Proposed features ===
			* Redunancy or Distributed nature for speed and relyability
	* 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 ===		=== Considerations ===

JeffM2501: /* Minimum Requirements */

2008-03-30T23:56:13Z

Minimum Requirements

← Older revision		Revision as of 23:56, 30 March 2008
Line 11:		Line 11:
	* Ability to list servers		* Ability to list servers
	** Player tracking (Who is where)		** Player tracking (Who is where)
	** Knowing if the server requests global auth or not		** Knowing if the server requests global auth or not (reg bit to tell people to reg)
	** Players on the server		** Players on the server
	** Team sizes (max and current)		** Team sizes (max and current)
	** Custom server status info (Game timer, game status)		** Custom server status info (Game timer, game status)
	** Restricting server visibility by global group		** Restricting server visibility by global group (advertise)
			** Get org names from the group manager for client sorting
	* 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 ===

JeffM2501 at 23:55, 30 March 2008

2008-03-30T23:55:10Z

← Older revision		Revision as of 23:55, 30 March 2008
Line 11:		Line 11:
	* Ability to list servers		* Ability to list servers
	** Player tracking (Who is where)		** Player tracking (Who is where)
	** Knowing ~~minimum requirements to talk, join, and spawn~~		** Knowing if the server requests global auth or not
	** Players on the server		** Players on the server
	** Team sizes (max and current)		** Team sizes (max and current)

AAA: More details

2008-03-30T23:52:24Z

More details

← Older revision		Revision as of 23:52, 30 March 2008
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 ~~needs~~ the following minimum 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		* 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
	* Image uploading
	* 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

AAA: Initial import

2008-03-30T23:46:52Z

Initial import

New page

{{DesignDocument}}
This is a proposal for a revamped BZFlag services system (list server, BZFlag forum, and website) by AAA.
Post comments on the [[Talk:BZFlag_Services_Proposal|Discussion page]]

== Minimum Requirements ==
The BZFlag global service needs the following minimum features:
* 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
* Image uploading
* 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