Jump to: navigation, search

Features/Sugar Update Control ASLO

343 bytes removed, 18:11, 14 August 2009
update information
== Summary ==
Modify the existing Sugar Update Control to pull from ASLO instead of the
== Owner ==
== Current status ==
* Targeted release: .86
* Last updated: 16 30 July 2009* Percentage of completion: 5075% All basic functionality is present. Needs testing.
== Source ==
== Detailed Description ==
Current, the Sugar Update Control pulls enables users to update their installed activities from wikithe Activities Library at Server side, this results in unnecessary work for activities developers as they must update specific wiki pages when releasing new activitiesActivities.sugarlabs. The existing system org is rather fragile as developers must store base on the update information by hand in machine-readable micro-formatwell established addons.mozilla. FWIW, this system was pretty good until ASLO came alongorg.
Using ASLO the client can request information about updated by sending a url of the form
== Benefit to Sugar ==
1. This benefits Sugar by moving the entire activities infrastructure to aslo rather than being spread across a wiki and aslo.
2. It reduces activity developer work loadby using the established upload process to update activities.
3. It reduces and isolates infrastructure load between wiki,, and download system. a. ASLO provides all necessary update information in a single network transaction. b. ASLO is backed by memcache, so standard update pings are _very_ very cheap. c. ASLO can be configured to store and serve downloads from download-farm to ease scaling issues.  Makes activities developers and infrastructure maintainers lives easier.
== Scope ==
Technically the scope is pretty limited. Most of the changes are inside sugar-update-control or are in ASLO.
There will not be external api changes.
Depends on the bitfrost python modules. Until a decision is made concerning where to include those modules in Sugar,, and are shipped with sugar-update-control. Socially, this is _huge_ change. Over the last several months, ASLO has been improving and proving it's reliability. Many activities are being served via ASLO as their information is marked deprecated on Shifting update to point to also will require clear communication to end users and developers.
=== Implementation ===

Navigation menu