Features/Automatic activity updates: Difference between revisions

(2 intermediate revisions by one other user not shown)

Line 1:

[[Category:Feature Page Incomplete]]

[[Category:~~Feature~~|Automatic activity updates]]

[[Category:FeatureLanded|Automatic activity updates]]

</noinclude>

Line 58:

To handle periodic updates (when system upgrades have not happened), 10 minutes after launch, Sugar will check if sufficient time has passed since the last successful update. If a configured threshold has been met, an activity update will be run. This check will then be repeated at 60 minute intervals.

The activity-update-urgent flag is set based on the presence of the file <tt>~/.sugar~~/default/activity_update_urgent~~</tt>.

The activity-update-urgent flag is set based on the presence of the file <tt>~/.sugar-update</tt>.

When an update successfully completes, the update time is recorded in the gconf key <tt>/desktop/sugar/update/last_activity_update</tt>. The amount of time that passes before an automatic activity update is executed is defined by the gconf key <tt>/desktop/sugar/update/auto_update_frequency</tt>, units in days, default 0 (which means no periodic update).

The gconf key <tt>/desktop/sugar/update/~~activity_update_mechanism~~</tt> will specify which update mechanism to use (ASLO or microformat), and the <tt>/desktop/sugar/update/~~activity_update_uri~~</tt> gconf key will specify the base server URI to use.

The gconf key <tt>/desktop/sugar/update/backend</tt> will specify which update mechanism to use (ASLO or microformat), and the <tt>/desktop/sugar/update/microformat_update_url</tt> gconf key will specify the base server URI to use for the microformat update backend.

The idea is that the deployer sets the appropriate gconf keys according to his preferences and infrastructure.

The core of the activity update code (src/extensions/cpsection/update/model.py and the backends) will be moved into src/jarabe/model/update, where it will be shared between the activity update control panel, and the automatic background update.

@@ Line 1: / Line 1: @@
 <noinclude>
 [[Category:Feature Page Incomplete]]
-[[Category:Feature|Automatic activity updates]]
+[[Category:FeatureLanded|Automatic activity updates]]
 </noinclude>
@@ Line 58: / Line 58: @@
 To handle periodic updates (when system upgrades have not happened), 10 minutes after launch, Sugar will check if sufficient time has passed since the last successful update. If a configured threshold has been met, an activity update will be run. This check will then be repeated at 60 minute intervals.
-The activity-update-urgent flag is set based on the presence of the file <tt>~/.sugar/default/activity_update_urgent</tt>.
+The activity-update-urgent flag is set based on the presence of the file <tt>~/.sugar-update</tt>.
 When an update successfully completes, the update time is recorded in the gconf key <tt>/desktop/sugar/update/last_activity_update</tt>. The amount of time that passes before an automatic activity update is executed is defined by the gconf key <tt>/desktop/sugar/update/auto_update_frequency</tt>, units in days, default 0 (which means no periodic update).
-The gconf key <tt>/desktop/sugar/update/activity_update_mechanism</tt> will specify which update mechanism to use (ASLO or microformat), and the <tt>/desktop/sugar/update/activity_update_uri</tt> gconf key will specify the base server URI to use.
+The gconf key <tt>/desktop/sugar/update/backend</tt> will specify which update mechanism to use (ASLO or microformat), and the <tt>/desktop/sugar/update/microformat_update_url</tt> gconf key will specify the base server URI to use for the microformat update backend.
+The idea is that the deployer sets the appropriate gconf keys according to his preferences and infrastructure.
 The core of the activity update code (src/extensions/cpsection/update/model.py and the backends) will be moved into src/jarabe/model/update, where it will be shared between the activity update control panel, and the automatic background update.