GSoC Reconnect Host change - Revision history

Abma: /* Possible Mentor(s) */

2012-03-02T17:54:42Z

Possible Mentor(s)

← Older revision		Revision as of 18:54, 2 March 2012
Line 20:		Line 20:
	* During a server switch extra measures need to be implemented to prevent cheating.		* During a server switch extra measures need to be implemented to prevent cheating.

	~~== Possible Mentor(s) ==~~		[[Category:GSoC]]

	~~{{GSoC2010_bottom}}~~

Koshi: backlink and category via template

2010-03-13T17:20:30Z

backlink and category via template

← Older revision		Revision as of 18:20, 13 March 2010
Line 22:		Line 22:
	== Possible Mentor(s) ==		== Possible Mentor(s) ==

	~~[[Google_Summer_of_Code_2010]]~~		{{GSoC2010_bottom}}

Tobi: Protected "GSoC Reconnect Host change": protecting during application period [edit=sysop:move=sysop] (expires 22:00, 10 April 2010 (UTC))

2010-03-12T16:06:16Z

Protected "GSoC Reconnect Host change": protecting during application period [edit=sysop:move=sysop] (expires 22:00, 10 April 2010 (UTC))

← Older revision	Revision as of 17:06, 12 March 2010
(No difference)

Tobi: /* Possible Mentor(s) */

2010-03-12T15:54:02Z

Possible Mentor(s)

← Older revision		Revision as of 16:54, 12 March 2010
Line 21:		Line 21:

	== Possible Mentor(s) ==		== Possible Mentor(s) ==

	~~[http://www.example.com FORUMLINK]~~

	[[Google_Summer_of_Code_2010]]		[[Google_Summer_of_Code_2010]]

Brain damage: /* What */

2010-03-12T15:28:21Z

What

← Older revision		Revision as of 16:28, 12 March 2010
Line 5:		Line 5:

	== What ==		== What ==
	Spring's network model implies the ~~existance~~ of a server to host a battle. For various reasons the network link between host and clients can ~~die, so a~~ system should be designed to allow manual and/or automatic switching of the game's host (possibly using an existing player after testing load handling capabilities) and manual and/or automatic reconnection from client side if host remains the same.		Spring's network model implies the existence of a server to host a battle. For various reasons the network link between host and clients can be interrupted. A system should be designed to allow manual and/or automatic switching of the game's host (possibly using an existing player after testing load handling capabilities) and manual and/or automatic reconnection from client side if host remains the same.

	== Required skills ==		== Required skills ==

Brain damage at 15:19, 12 March 2010

2010-03-12T15:19:18Z

← Older revision		Revision as of 16:19, 12 March 2010
Line 3:		Line 3:
	== Why ==		== Why ==
	Network links can sometimes be unreliable, being able to overcome temporary issues will improve play experience.		Network links can sometimes be unreliable, being able to overcome temporary issues will improve play experience.
	== ~~Background~~ ==
			== What ==
	Spring's network model implies the existance of a server to host a battle. For various reasons the network link between host and clients can die, so a system should be designed to allow manual and/or automatic switching of the game's host (possibly using an existing player after testing load handling capabilities) and manual and/or automatic reconnection from client side if host remains the same.		Spring's network model implies the existance of a server to host a battle. For various reasons the network link between host and clients can die, so a system should be designed to allow manual and/or automatic switching of the game's host (possibly using an existing player after testing load handling capabilities) and manual and/or automatic reconnection from client side if host remains the same.

Line 13:		Line 14:
	== Difficulty ==		== Difficulty ==
	Estimated: medium to hard		Estimated: medium to hard

			== Technical details ==

	* During a drop-out clients can be at diverging points in simulation time (game frame), so any solution would have to determine a common point and bring all players to that to ensure sync.		* During a drop-out clients can be at diverging points in simulation time (game frame), so any solution would have to determine a common point and bring all players to that to ensure sync.

Brain damage: standardizing requirements format

2010-03-12T15:09:23Z

standardizing requirements format

← Older revision		Revision as of 16:09, 12 March 2010
Line 7:		Line 7:

	== Required skills ==		== Required skills ==
	* C++		* Knowledge of C++
	* General networking knowledge		* General networking knowledge
	* Boost::asio sockets		* Understanding Spring's networking model
	* Understanding Spring's networking

	== Difficulty ==		== Difficulty ==

Koshi: /* Difficulty */

2010-03-11T22:02:45Z

Difficulty

← Older revision		Revision as of 23:02, 11 March 2010
Line 15:		Line 15:
	Estimated: medium to hard		Estimated: medium to hard

	* During a drop-out~~, all~~ clients can ~~have different~~ frame ~~amount~~, ~~it needs~~ to determine a common point and bring all players to that to ensure sync		* During a drop-out clients can be at diverging points in simulation time (game frame), so any solution would have to determine a common point and bring all players to that to ensure sync.
	* During a server switch~~, particular~~ measures ~~should~~ be ~~adopted~~ to prevent cheating		* During a server switch extra measures need to be implemented to prevent cheating.

	== Possible Mentor(s) ==		== Possible Mentor(s) ==

Koshi: /* Background */

2010-03-11T21:58:53Z

Background

← Older revision		Revision as of 22:58, 11 March 2010
Line 4:		Line 4:
	Network links can sometimes be unreliable, being able to overcome temporary issues will improve play experience.		Network links can sometimes be unreliable, being able to overcome temporary issues will improve play experience.
	== Background ==		== Background ==
	Spring's network model implies the existance of a server to host a battle~~, because of~~ various reasons, the network link between host and clients can die, a system should be designed to allow manual and/or automatic ~~switch~~ game host (possibly using an existing player after testing load handling capabilities), and manual and/or automatic reconnection from client side if host remains the same.		Spring's network model implies the existance of a server to host a battle. For various reasons the network link between host and clients can die, so a system should be designed to allow manual and/or automatic switching of the game's host (possibly using an existing player after testing load handling capabilities) and manual and/or automatic reconnection from client side if host remains the same.

	== Required skills ==		== Required skills ==

Brain damage: New page: = GSoC idea: Reconnect / Host change during a match = == Why == Network links can sometimes be unreliable, being able to overcome temporary issues will improve play experience. == Backgr...

2010-03-11T21:55:25Z

New page: = GSoC idea: Reconnect / Host change during a match = == Why == Network links can sometimes be unreliable, being able to overcome temporary issues will improve play experience. == Backgr...

New page

= GSoC idea: Reconnect / Host change during a match =

== Why ==
Network links can sometimes be unreliable, being able to overcome temporary issues will improve play experience.
== Background ==
Spring's network model implies the existance of a server to host a battle, because of various reasons, the network link between host and clients can die, a system should be designed to allow manual and/or automatic switch game host (possibly using an existing player after testing load handling capabilities), and manual and/or automatic reconnection from client side if host remains the same.

== Required skills ==
* C++
* General networking knowledge
* Boost::asio sockets
* Understanding Spring's networking

== Difficulty ==
Estimated: medium to hard

* During a drop-out, all clients can have different frame amount, it needs to determine a common point and bring all players to that to ensure sync
* During a server switch, particular measures should be adopted to prevent cheating

== Possible Mentor(s) ==

[http://www.example.com FORUMLINK]

[[Google_Summer_of_Code_2010]]