SoC Ideas Network Stack Rewrite: Difference between revisions

From The Battle for Wesnoth Wiki
Crab (talk | contribs)
mNo edit summary
Crab (talk | contribs)
mNo edit summary
Line 2: Line 2:
= Description =
= Description =
<h3>Rewrite wesnoth network stack using boost::asio</h3>
<h3>Rewrite wesnoth network stack using boost::asio</h3>
Rewrite wesnoth network stack using boost::asio
Rewrite wesnoth network stack using boost::asio.
 
= Additional Information =
= 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:


= Details =
* 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)

Revision as of 22:11, 3 March 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

Rewrite wesnoth network stack using boost::asio.

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)
This page was last edited on 3 March 2010, at 22:11.
Cookies help us deliver our services. By using our services, you agree to our use of cookies.