SoC Ideas Network Stack Rewrite: Difference between revisions
From The Battle for Wesnoth Wiki
Created page with '{{Template:SoC2010}}' |
|||
| (11 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{Template: | {{Template:SoC2010Idea}} | ||
= Description = | |||
<h2>Rewrite wesnoth network stack using boost::asio</h2> | |||
Page for the idea: [[SoC_Ideas_Network_Stack_Rewrite]] | |||
Rewrite wesnoth network stack using boost::asio. | |||
{{#dpl: | |||
|resultsheader=''There are %PAGES% submitted student proposals for this idea'' | |||
|oneresultheader=''There is 1 submitted student proposal for this idea'' | |||
|notcategory=SoC 2010 Not Submitted To Google | |||
|suppresserrors=true | |||
|noresultsheader=''There are no submitted student proposals for this idea'' | |||
|category=Summer of Code 2010 Student Page&SoC Ideas Network Stack Rewrite | |||
|include=#Description | |||
|mode=userformat | |||
|format=,,<br/>See [[%PAGE%|%TITLE%]] for more information.<br/><br/>, | |||
}} | |||
= Additional Information = | |||
Currently, wesnoth uses 'sdl net' for network layer. There's a number of issues with it. We want to recode wesnoth network layer (wesnothd server, wesnoth client, stats uploader) using a framework like boost::asio. | |||
Features wanted: | |||
* proxy support. | |||
* configurable timeout value for connections. | |||
* ability for wesnoth client to multiplex connections to wesnoth server (allow client to connect to wesnoth server multiple times) | |||
* ability to use wesnoth network client with a different c++ backend (e.g., use wesnoth network client as a library) | |||
= Questions = | |||
* what proxies (authentication types) we can support, if we code a network stack using boost::asio, and how hard it'll be ? | |||
* what general architecture for the client you're going to use ? | |||
* what general architecture for the server you're going to use ? | |||
* how you'd allow the wesnoth client to multiplex connections to wesnoth server ? | |||
* how you'd make it possible to use wesnoth network client with a different c++ backend? | |||
* what problems and potential pitfalls do you see in the task? | |||
Latest revision as of 22:55, 9 April 2010
| This page is related to Summer of Code 2010 |
| See the list of Summer of Code 2010 Ideas |
| This is a Summer of Code 2010 Idea |
Description
Rewrite wesnoth network stack using boost::asio
Page for the idea: SoC_Ideas_Network_Stack_Rewrite
Rewrite wesnoth network stack using boost::asio.
There are no submitted student proposals for this idea
Additional Information
Currently, wesnoth uses 'sdl net' for network layer. There's a number of issues with it. We want to recode wesnoth network layer (wesnothd server, wesnoth client, stats uploader) using a framework like boost::asio. Features wanted:
- proxy support.
- configurable timeout value for connections.
- ability for wesnoth client to multiplex connections to wesnoth server (allow client to connect to wesnoth server multiple times)
- ability to use wesnoth network client with a different c++ backend (e.g., use wesnoth network client as a library)
Questions
- what proxies (authentication types) we can support, if we code a network stack using boost::asio, and how hard it'll be ?
- what general architecture for the client you're going to use ?
- what general architecture for the server you're going to use ?
- how you'd allow the wesnoth client to multiplex connections to wesnoth server ?
- how you'd make it possible to use wesnoth network client with a different c++ backend?
- what problems and potential pitfalls do you see in the task?
This page was last edited on 9 April 2010, at 22:55.