BZFS2 prototype - Revision history

Blast: Reverted edits by Zehra (talk) to last revision by JeffM2501

2017-02-12T14:13:29Z

Reverted edits by Zehra (talk) to last revision by JeffM2501

← Older revision		Revision as of 14:13, 12 February 2017
Line 1:		Line 1:
	~~#REDIRECT [[~~BZFS]]		{{IdeaDesign}}
			''This is an overview of the BZFS2 prototype released 4/22/2007.''
			''This document describes a proof of concept rewrite of BZFS, it does not represent the current state of any release or version of the main project code.''
			==The New Paradigms==
			'''Channel''' - Channels are for transmitting various data at different priorities and with different rights. Players 'tune in' and 'tune out' of channels depending on the state they are in and the rights that are conferred to them.

			The channel model has a super channel which every client is connected to immediately upon connecting to the server. Then, there are one or more game channels where the game is actually played, and any game-related data is sent within this channel. There is at least one admin channel which authenticated users are tuned in to for admin-specific data.

			'''Group''' - The new security model is a layered grouping model. All entities (players, channels, other groups), are within a group, and rights for any entity depend on the rights of a group and all it's ancestor groups.

			'''Task''' - Tasks can be running tasks or timed tasks, and can be registered either from the server, or from plug-ins.
			==Networking==
			Networking is now separate from player data. The base class is Client (Similar to the NetConnectedPeer), with children LocalClient and RemoteClient (RelayClient is planned). The Client abstracts the network implementation away from the server. RemoteClient uses basic sockets, ENetRemoteClient will use ENet, SDLRemoteClient will use SDL-Net.

			Message are queued and directed by the Channel. Broadcast messages are broadcast to clients tuned to the channel. Only messages broadcast on the super channel are guaranteed to reach every connected client.

			'''Relay Servers''' - One method of handling latency over long distances is a relay server, which clients local to the this relay connect to it, and the relay connects to the main server. Messages both ways are batched and fewer packets are sent between a relay and the main than between the main and a direct client player.
			==Game State==
			This server engine is designed to allow game state to be kept by the server in an abstracted form. How this will be implemented is yet to be decided.
			==Plug-ins==
			Several functions that are part of the current BZFS have been removed to be implemented as plug-ins instead. This includes admin functions and voting. This means the server would be packaged with several default plug-ins that add core functionality.

			==API==
			Additional API is required to support the admin function plugin, and allow plug-ins to register tasks and commands. By and large, the API does remain the same.

Zehra: redirecting page as no content links to it (also it appears concept is no longer worked on.)

2017-02-08T20:34:11Z

redirecting page as no content links to it (also it appears concept is no longer worked on.)

← Older revision		Revision as of 20:34, 8 February 2017
Line 1:		Line 1:
	~~{{IdeaDesign}}~~		#REDIRECT [[BZFS]]
	~~''This is an overview of the BZFS2 prototype released 4/22/2007.''~~
	~~''This document describes a proof of concept rewrite of~~ BZFS~~, it does not represent the current state of any release or version of the main project code.''~~
	~~==The New Paradigms==~~
	'''Channel''' - Channels are for transmitting various data at different priorities and with different rights. Players 'tune in' and 'tune out' of channels depending on the state they are in and the rights that are conferred to them.

	The channel model has a super channel which every client is connected to immediately upon connecting to the server. Then, there are one or more game channels where the game is actually played, and any game-related data is sent within this channel. There is at least one admin channel which authenticated users are tuned in to for admin-specific data.

	'''Group''' - The new security model is a layered grouping model. All entities (players, channels, other groups), are within a group, and rights for any entity depend on the rights of a group and all it's ancestor groups.

	~~'''Task''' - Tasks can be running tasks or timed tasks, and can be registered either from the server, or from plug-ins.~~
	~~==Networking==~~
	Networking is now separate from player data. The base class is Client (Similar to the NetConnectedPeer), with children LocalClient and RemoteClient (RelayClient is planned). The Client abstracts the network implementation away from the server. RemoteClient uses basic sockets, ENetRemoteClient will use ENet, SDLRemoteClient will use SDL-Net.

	Message are queued and directed by the Channel. Broadcast messages are broadcast to clients tuned to the channel. Only messages broadcast on the super channel are guaranteed to reach every connected client.

	'''Relay Servers''' - One method of handling latency over long distances is a relay server, which clients local to the this relay connect to it, and the relay connects to the main server. Messages both ways are batched and fewer packets are sent between a relay and the main than between the main and a direct client player.
	~~==Game State==~~
	~~This server engine is designed to allow game state to be kept by the server in an abstracted form. How this will be implemented is yet to be decided.~~
	~~==Plug-ins==~~
	Several functions that are part of the current BZFS have been removed to be implemented as plug-ins instead. This includes admin functions and voting. This means the server would be packaged with several default plug-ins that add core functionality.

	~~==API==~~
	~~Additional API is required to support the admin function plugin, and allow plug-ins to register tasks and commands. By and large, the API does remain the same.~~

JeffM2501: move to IdeaDesign

2013-02-10T08:05:23Z

move to IdeaDesign

← Older revision		Revision as of 08:05, 10 February 2013
Line 1:		Line 1:
	{{~~DesignDocument~~}}		{{IdeaDesign}}
	''This is an overview of the BZFS2 prototype released 4/22/2007.''		''This is an overview of the BZFS2 prototype released 4/22/2007.''
	''This document describes a proof of concept rewrite of BZFS, it does not represent the current state of any release or version of the main project code.''		''This document describes a proof of concept rewrite of BZFS, it does not represent the current state of any release or version of the main project code.''
Line 23:		Line 23:
	==API==		==API==
	Additional API is required to support the admin function plugin, and allow plug-ins to register tasks and commands. By and large, the API does remain the same.		Additional API is required to support the admin function plugin, and allow plug-ins to register tasks and commands. By and large, the API does remain the same.


	~~[[Category:Unapproved Development Ideas]]~~

JeffM2501: Fix categories

2013-02-10T08:02:12Z

Fix categories

← Older revision		Revision as of 08:02, 10 February 2013
Line 23:		Line 23:
	==API==		==API==
	Additional API is required to support the admin function plugin, and allow plug-ins to register tasks and commands. By and large, the API does remain the same.		Additional API is required to support the admin function plugin, and allow plug-ins to register tasks and commands. By and large, the API does remain the same.
	~~==See also==~~
	[[Category:~~Enhancements~~]]
			[[Category:Unapproved Development Ideas]]

Joevano: /* Plug-ins */

2007-05-23T12:11:41Z

Plug-ins

← Older revision		Revision as of 12:11, 23 May 2007
Line 19:		Line 19:
	This server engine is designed to allow game state to be kept by the server in an abstracted form. How this will be implemented is yet to be decided.		This server engine is designed to allow game state to be kept by the server in an abstracted form. How this will be implemented is yet to be decided.
	==Plug-ins==		==Plug-ins==
	Several functions that are part of current BZFS have been removed to be plug-ins instead. This includes admin functions and voting. This means the server would be packaged with several default plug-ins that add core functionality.		Several functions that are part of the current BZFS have been removed to be implemented as plug-ins instead. This includes admin functions and voting. This means the server would be packaged with several default plug-ins that add core functionality.

	==API==		==API==

68.90.161.137: /* Plug-ins */

2007-05-23T03:34:48Z

Plug-ins

← Older revision		Revision as of 03:34, 23 May 2007
Line 19:		Line 19:
	This server engine is designed to allow game state to be kept by the server in an abstracted form. How this will be implemented is yet to be decided.		This server engine is designed to allow game state to be kept by the server in an abstracted form. How this will be implemented is yet to be decided.
	==Plug-ins==		==Plug-ins==
	Several functions that are part of BZFS ~~currently~~ have been removed to be plug-ins instead. This includes admin functions and voting. This means the server would be packaged with several default plug-ins that add core functionality.		Several functions that are part of current BZFS have been removed to be plug-ins instead. This includes admin functions and voting. This means the server would be packaged with several default plug-ins that add core functionality.

	==API==		==API==
	Additional API is required to support the admin function plugin, and allow plug-ins to register tasks and commands. By and large, the API does remain the same.		Additional API is required to support the admin function plugin, and allow plug-ins to register tasks and commands. By and large, the API does remain the same.
	==See also==		==See also==
	[[Category:Enhancements]]		[[Category:Enhancements]]

70.12.89.48 at 16:32, 26 April 2007

2007-04-26T16:32:03Z

← Older revision		Revision as of 16:32, 26 April 2007
Line 11:		Line 11:
	'''Task''' - Tasks can be running tasks or timed tasks, and can be registered either from the server, or from plug-ins.		'''Task''' - Tasks can be running tasks or timed tasks, and can be registered either from the server, or from plug-ins.
	==Networking==		==Networking==
	Networking is now separate from player data. The base class is Client, with children LocalClient and RemoteClient (RelayClient is planned). The Client abstracts the network implementation away from the server. RemoteClient uses basic sockets, ENetRemoteClient will use ENet, SDLRemoteClient will use SDL-Net.		Networking is now separate from player data. The base class is Client (Similar to the NetConnectedPeer), with children LocalClient and RemoteClient (RelayClient is planned). The Client abstracts the network implementation away from the server. RemoteClient uses basic sockets, ENetRemoteClient will use ENet, SDLRemoteClient will use SDL-Net.

	Message are queued and directed by the Channel. Broadcast messages are broadcast to clients tuned to the channel. Only messages broadcast on the super channel are guaranteed to reach every connected client.		Message are queued and directed by the Channel. Broadcast messages are broadcast to clients tuned to the channel. Only messages broadcast on the super channel are guaranteed to reach every connected client.

Joevano at 17:21, 23 April 2007

2007-04-23T17:21:38Z

← Older revision		Revision as of 17:21, 23 April 2007
Line 1:		Line 1:
	{{DesignDocument}}		{{DesignDocument}}

	''This is an overview of the BZFS2 prototype released 4/22/2007.''		''This is an overview of the BZFS2 prototype released 4/22/2007.''
	''This document describes a proof of concept rewrite of BZFS, it does not represent the current state of any release or version of the main project code.''		''This document describes a proof of concept rewrite of BZFS, it does not represent the current state of any release or version of the main project code.''

	==The New Paradigms==		==The New Paradigms==

	'''Channel''' - Channels are for transmitting various data at different priorities and with different rights. Players 'tune in' and 'tune out' of channels depending on the state they are in and the rights that are conferred to them.		'''Channel''' - Channels are for transmitting various data at different priorities and with different rights. Players 'tune in' and 'tune out' of channels depending on the state they are in and the rights that are conferred to them.

Line 13:		Line 10:

	'''Task''' - Tasks can be running tasks or timed tasks, and can be registered either from the server, or from plug-ins.		'''Task''' - Tasks can be running tasks or timed tasks, and can be registered either from the server, or from plug-ins.

	==Networking==		==Networking==

	Networking is now separate from player data. The base class is Client, with children LocalClient and RemoteClient (RelayClient is planned). The Client abstracts the network implementation away from the server. RemoteClient uses basic sockets, ENetRemoteClient will use ENet, SDLRemoteClient will use SDL-Net.		Networking is now separate from player data. The base class is Client, with children LocalClient and RemoteClient (RelayClient is planned). The Client abstracts the network implementation away from the server. RemoteClient uses basic sockets, ENetRemoteClient will use ENet, SDLRemoteClient will use SDL-Net.

Line 21:		Line 16:

	'''Relay Servers''' - One method of handling latency over long distances is a relay server, which clients local to the this relay connect to it, and the relay connects to the main server. Messages both ways are batched and fewer packets are sent between a relay and the main than between the main and a direct client player.		'''Relay Servers''' - One method of handling latency over long distances is a relay server, which clients local to the this relay connect to it, and the relay connects to the main server. Messages both ways are batched and fewer packets are sent between a relay and the main than between the main and a direct client player.

	==Game State==		==Game State==

	This server engine is designed to allow game state to be kept by the server in an abstracted form. How this will be implemented is yet to be decided.		This server engine is designed to allow game state to be kept by the server in an abstracted form. How this will be implemented is yet to be decided.

	==Plug-ins==		==Plug-ins==

	Several functions that are part of BZFS currently have been removed to be plug-ins instead. This includes admin functions and voting. This means the server would be packaged with several default plug-ins that add core functionality.		Several functions that are part of BZFS currently have been removed to be plug-ins instead. This includes admin functions and voting. This means the server would be packaged with several default plug-ins that add core functionality.

	==API==		==API==

	Additional API is required to support the admin function plugin, and allow plug-ins to register tasks and commands. By and large, the API does remain the same.		Additional API is required to support the admin function plugin, and allow plug-ins to register tasks and commands. By and large, the API does remain the same.

	==See also==		==See also==
	[[Category:Enhancements]]		[[Category:Enhancements]]

Joevano: Spelling

2007-04-23T17:20:28Z

Spelling

← Older revision		Revision as of 17:20, 23 April 2007
Line 2:		Line 2:

	''This is an overview of the BZFS2 prototype released 4/22/2007.''		''This is an overview of the BZFS2 prototype released 4/22/2007.''
	''This document describes a proof of concept ~~rewite~~ of BZFS, it does not represent the current state of any release or version of the main project code.''		''This document describes a proof of concept rewrite of BZFS, it does not represent the current state of any release or version of the main project code.''

	==The New Paradigms==		==The New Paradigms==
Line 12:		Line 12:
	'''Group''' - The new security model is a layered grouping model. All entities (players, channels, other groups), are within a group, and rights for any entity depend on the rights of a group and all it's ancestor groups.		'''Group''' - The new security model is a layered grouping model. All entities (players, channels, other groups), are within a group, and rights for any entity depend on the rights of a group and all it's ancestor groups.

	'''Task''' - Tasks can be running tasks or timed tasks, and can be registered either from the server, or from ~~plugins~~.		'''Task''' - Tasks can be running tasks or timed tasks, and can be registered either from the server, or from plug-ins.

	==Networking==		==Networking==
Line 26:		Line 26:
	This server engine is designed to allow game state to be kept by the server in an abstracted form. How this will be implemented is yet to be decided.		This server engine is designed to allow game state to be kept by the server in an abstracted form. How this will be implemented is yet to be decided.

	==~~Plugins~~==		==Plug-ins==

	Several functions that are part of BZFS currently have been removed to be ~~plugins~~ instead. This includes admin functions and voting. This means the server would be packaged with several default ~~plugins~~ that add core functionality.		Several functions that are part of BZFS currently have been removed to be plug-ins instead. This includes admin functions and voting. This means the server would be packaged with several default plug-ins that add core functionality.

	==API==		==API==

	Additional API is required to support the admin function plugin, and allow ~~plugins~~ to register tasks and commands. By and large, the API does remain the same.		Additional API is required to support the admin function plugin, and allow plug-ins to register tasks and commands. By and large, the API does remain the same.

	==See also==		==See also==
	[[Category:Enhancements]]		[[Category:Enhancements]]

JeffM2501 at 17:19, 23 April 2007

2007-04-23T17:19:05Z

← Older revision		Revision as of 17:19, 23 April 2007
Line 2:		Line 2:

	''This is an overview of the BZFS2 prototype released 4/22/2007.''		''This is an overview of the BZFS2 prototype released 4/22/2007.''
			''This document describes a proof of concept rewite of BZFS, it does not represent the current state of any release or version of the main project code.''

	==The New Paradigms==		==The New Paradigms==