User:Vinipsmaker/GSoC13/Proposal - Revision history

Vultraz: Dropped link to BinaryWML

2015-04-22T06:51:14Z

Dropped link to BinaryWML

← Older revision		Revision as of 06:51, 22 April 2015
Line 119:		Line 119:
	=== The ''new'' protocol ===		=== The ''new'' protocol ===

	The new protocol purpose is to address limitations faced in current protocol. For the new protocol, [[BinaryWML]] still will be used, to ease integration with Wesnoth client. The protocol is case-sensitive.		The new protocol purpose is to address limitations faced in current protocol. For the new protocol, BinaryWML still will be used, to ease integration with Wesnoth client. The protocol is case-sensitive.

	* From now on, messages will use error codes (similar, but not equal, to HTTP and JSON-RPC). This behaviour is useful to build automated tools and to show customized (read translated) message errors to users. '''The message errors will still be WML-based.'''		* From now on, messages will use error codes (similar, but not equal, to HTTP and JSON-RPC). This behaviour is useful to build automated tools and to show customized (read translated) message errors to users. '''The message errors will still be WML-based.'''

Vinipsmaker: /* Timeline */

2013-05-20T19:29:08Z

Timeline

← Older revision		Revision as of 19:29, 20 May 2013
Line 196:		Line 196:
	* Documentation should follow it progress.		* Documentation should follow it progress.
	\|-		\|-
	\| Week 8 (July 14 to 20) \|\| Introduce threads ~~and SSL.~~ \|\| Mandatory ~~for threads and optional for~~ SSL \|\|		\| Week 8 (July 14 to 20) \|\| Introduce threads \|\| Mandatory \|\|
			\|-
			\| Week 8 (July 14 to 20) \|\| Introduce SSL \|\| Optional \|\|
	\|-		\|-
	\| Week 9-11 (July 21 till August 10) \|\| LDAP support \|\| Mandatory \|\| It may take less time, but I'm overestimating because I have little experience with LDAP (only as a sysadmin at [http://en.lccv.ufal.br/cluster/ LCCV] for a while)		\| Week 9-11 (July 21 till August 10) \|\| LDAP support \|\| Mandatory \|\| It may take less time, but I'm overestimating because I have little experience with LDAP (only as a sysadmin at [http://en.lccv.ufal.br/cluster/ LCCV] for a while)

Vinipsmaker: /* Timeline */

2013-05-19T22:52:02Z

Timeline

← Older revision		Revision as of 22:52, 19 May 2013
Line 178:		Line 178:
	\|-		\|-
	\| Week -1 (May 12 to 18) \|\| Install a Debian chroot in my system that mimics Wesnoth main server.		\| Week -1 (May 12 to 18) \|\| Install a Debian chroot in my system that mimics Wesnoth main server.
	\| ~~style~~="~~background:~~ #00FF00;" \| DONE		\| bgcolor="#00FF00" \| DONE
	\|\| Debian 6.0 (squeeze) with [http://wiki.wesnoth.org/CompilingWesnoth#Prerequisites all Wesnoth build deps] (tested)		\|\| Debian 6.0 (squeeze) with [http://wiki.wesnoth.org/CompilingWesnoth#Prerequisites all Wesnoth build deps] (tested)
	\|-		\|-

Vinipsmaker: /* Timeline */

2013-05-19T22:41:04Z

Timeline

← Older revision		Revision as of 22:41, 19 May 2013
Line 177:		Line 177:
	! Period !! Task !! Status !! Notes		! Period !! Task !! Status !! Notes
	\|-		\|-
	\| Week -1 (May 12 to 18) \|\| Install a Debian chroot in my system that mimics Wesnoth main server. \|\| ~~Mandatory~~ \|\|		\| Week -1 (May 12 to 18) \|\| Install a Debian chroot in my system that mimics Wesnoth main server.
			\| style="background: #00FF00;" \| DONE
			\|\| Debian 6.0 (squeeze) with [http://wiki.wesnoth.org/CompilingWesnoth#Prerequisites all Wesnoth build deps] (tested)
	\|-		\|-
	\| Week 0 (May 19 to 25) \|\| Create a Wesnoth branch and start coding. Get used to Boost.asio. \|\| Mandatory \|\|		\| Week 0 (May 19 to 25) \|\| Create a Wesnoth branch and start coding. Get used to Boost.asio. \|\| Mandatory \|\|

Vinipsmaker: fix small gramar issue

2013-05-19T20:58:15Z

fix small gramar issue

← Older revision		Revision as of 20:58, 19 May 2013
Line 184:		Line 184:
	\|-		\|-
	\| Week 3 (June 9 to 15) \|\| Reimplement a subset of the current protocol in Boost.asio. \|\| Optional \|\|		\| Week 3 (June 9 to 15) \|\| Reimplement a subset of the current protocol in Boost.asio. \|\| Optional \|\|
	* This feature will ~~depends~~ on the event loop		* This feature will depend on the event loop
	* It'll delegate the '''read''' operations to the database		* It'll delegate the '''read''' operations to the database
	\|-		\|-

Vinipsmaker: /* Event loop != boost::io_service */

2013-05-19T20:11:45Z

Event loop != boost::io_service

← Older revision		Revision as of 20:11, 19 May 2013
Line 69:		Line 69:
	=== Event loop != boost::io_service ===		=== Event loop != boost::io_service ===

	The boost::io_service object has [http://www.boost.org/doc/libs/1_42_0/doc/html/boost_asio/reference/io_service/run.html an option] to act as an event loop, but this option may be suboptiomal when we want to schedule our own actions. So, I'd implement my own event loop class, allowing anyone to register its own actions and [http://www.boost.org/doc/libs/1_42_0/doc/html/boost_asio/reference/io_service/poll.html integrate it with io_service].		The boost::io_service object has [http://www.boost.org/doc/libs/1_42_0/doc/html/boost_asio/reference/io_service/run.html an option] to act as an event loop, but this option may be suboptiomal when we want to schedule our own actions. Suppose we need to acquire some mutex, then we can't use ''[http://www.boost.org/doc/libs/1_42_0/doc/html/thread/synchronization.html#thread.synchronization.mutex_concepts.lockable.try_lock try_lock]'' because we can't schedule our own actions if it's not I/O related. So, I'd implement my own event loop class, allowing anyone to register its own actions and [http://www.boost.org/doc/libs/1_42_0/doc/html/boost_asio/reference/io_service/poll.html integrate it with io_service].

	To avoid locking a thread for more time than necessary, the EventLoop class would allow to register a delayed action in some queue. The actions that require lock would use try_lock (in conjunction with lock guard, to maintain the RAII idiom) in combination with delayed actions to block the current event loop as little as possible.		To avoid locking a thread for more time than necessary, the EventLoop class would allow to register a delayed action in some queue. The actions that require lock would use try_lock (in conjunction with lock guard, to maintain the RAII idiom) in combination with delayed actions to block the current event loop as little as possible.

Vinipsmaker: /* Timeline */

2013-05-19T20:03:55Z

Timeline

← Older revision		Revision as of 20:03, 19 May 2013
Line 181:		Line 181:
	\| Week 0 (May 19 to 25) \|\| Create a Wesnoth branch and start coding. Get used to Boost.asio. \|\| Mandatory \|\|		\| Week 0 (May 19 to 25) \|\| Create a Wesnoth branch and start coding. Get used to Boost.asio. \|\| Mandatory \|\|
	\|-		\|-
	\| Week 1-2 (May 26 till June 8) \|\| Create the SimpleAddonManager, capable of execute the operations needed to manage add-ons. \|\| Mandatory \|\|		\| Week 1-2 (May 26 till June 8) \|\| Create the SimpleAddonManager, capable of execute the operations needed to manage add-ons. \|\| Mandatory \|\| The base to better meta-data and i18n support.
	\|-		\|-
	\| Week 3 (June 9 to 15) \|\| Reimplement the current protocol in Boost.asio. \|\| ~~Mandatory~~ \|\|		\| Week 3 (June 9 to 15) \|\| Reimplement a subset of the current protocol in Boost.asio. \|\| Optional \|\|
			* This feature will depends on the event loop
			* It'll delegate the '''read''' operations to the database
	\|-		\|-
	\| Week 4 (June 16 to 22) \|\| Start working on the authentication support. \|\| Mandatory \|\|		\| Week 4 (June 16 to 22) \|\| Start working on the authentication support. \|\| Mandatory \|\| The standalone login backend won't support access control groups
	\|-		\|-
	\| Week 5-7 (June 23 till July 13) \|\| Implement the new protocol \|\| Mandatory \|\| Documentation should follow it progress.		\| Week 5-7 (June 23 till July 13) \|\| Implement the new protocol \|\| Mandatory \|\|
			* It'll delegate '''read''' and '''write''' operations to the database.
			* It'll be integrated with the authentication support.
			* Documentation should follow it progress.
	\|-		\|-
	\| Week 8 (July 14 to 20) \|\| Introduce threads and SSL. \|\| Mandatory \|\|		\| Week 8 (July 14 to 20) \|\| Introduce threads and SSL. \|\| Mandatory for threads and optional for SSL \|\|
	\|-		\|-
	\| Week 9-11 (July 21 till August 10) \|\| LDAP support \|\| Mandatory \|\|		\| Week 9-11 (July 21 till August 10) \|\| LDAP support \|\| Mandatory \|\| It may take less time, but I'm overestimating because I have little experience with LDAP (only as a sysadmin at [http://en.lccv.ufal.br/cluster/ LCCV] for a while)
	\|-		\|-
	\| Week 12 (August 11 to 17) \|\| Do more tests, fix bugs and integrate the new branch into the Wesnoth main branch \|\| Mandatory \|\|		\| Week 12 (August 11 to 17) \|\| Do more tests, fix bugs and integrate the new branch into the Wesnoth main branch \|\| Mandatory \|\|

Vinipsmaker: timeline: convert from list to table

2013-05-19T19:02:25Z

timeline: convert from list to table

← Older revision		Revision as of 19:02, 19 May 2013
Line 173:		Line 173:
	== Timeline ==		== Timeline ==

	* Week -1 (May 12 to 18): Install a Debian chroot in my system that mimics Wesnoth main server. ~~''(mandatory)''~~		{\| class="wikitable"
	* Week 0 (May 19 to 25): Create a Wesnoth branch and start coding. Get used to Boost.asio ~~''(mandatory)''~~		\|-
	* Week 1-2 (May 26 till June 8): Create the SimpleAddonManager, capable of execute the operations needed to manage add-ons. ~~''(mandatory)''~~		! Period !! Task !! Status !! Notes
	* Week 3 (June 9 to 15): Reimplement the current protocol in Boost.asio. ~~''(mandatory)''~~		\|-
	* Week 4 (June 16 to 22): Start working on the authentication support ~~''(mandatory)''~~		\| Week -1 (May 12 to 18) \|\| Install a Debian chroot in my system that mimics Wesnoth main server. \|\| Mandatory \|\|
	* Week 5-7 (June 23 till July 13): Implement the new protocol ~~(documentation~~ should follow it progress). ~~''(mandatory)''~~		\|-
	* Week 8 (July 14 to 20): Introduce threads and SSL ~~''(mandatory)''~~		\| Week 0 (May 19 to 25) \|\| Create a Wesnoth branch and start coding. Get used to Boost.asio. \|\| Mandatory \|\|
	* Week 9-11 (July 21 till August 10): LDAP support ~~''(mandatory)''~~		\|-
	* Week 12 (August 11 to 17): Do more tests, fix bugs and integrate the new branch into the Wesnoth main branch ~~''(mandatory)''~~		\| Week 1-2 (May 26 till June 8) \|\| Create the SimpleAddonManager, capable of execute the operations needed to manage add-ons. \|\| Mandatory \|\|
	* Week 13-16 (August 18 till September 14): Integrate the new protocol in Wesnoth client ~~''(mandatory)''~~		\|-
			\| Week 3 (June 9 to 15) \|\| Reimplement the current protocol in Boost.asio. \|\| Mandatory \|\|
			\|-
			\| Week 4 (June 16 to 22) \|\| Start working on the authentication support. \|\| Mandatory \|\|
			\|-
			\| Week 5-7 (June 23 till July 13) \|\| Implement the new protocol \|\| Mandatory \|\| Documentation should follow it progress.
			\|-
			\| Week 8 (July 14 to 20) \|\| Introduce threads and SSL. \|\| Mandatory \|\|
			\|-
			\| Week 9-11 (July 21 till August 10) \|\| LDAP support \|\| Mandatory \|\|
			\|-
			\| Week 12 (August 11 to 17) \|\| Do more tests, fix bugs and integrate the new branch into the Wesnoth main branch \|\| Mandatory \|\|
			\|-
			\| Week 13-16 (August 18 till September 14) \|\| Integrate the new protocol in Wesnoth client. \|\| Mandatory \|\|
			\|}

	I overestimated all tasks, so I may finish some tasks a bit sooner and use this time to compensate the wrongly estimated tasks, but this made the timeline lose some precision.		I overestimated all tasks, so I may finish some tasks a bit sooner and use this time to compensate the wrongly estimated tasks, but this made the timeline lose some precision.

Vinipsmaker at 20:49, 17 May 2013

2013-05-17T20:49:57Z

Show changes

Vinipsmaker at 05:30, 9 May 2013

2013-05-09T05:30:35Z

Show changes