One of the features module authors can take advantage of is the module auto-updating capabilities. This allows, without any additional code in the module, for the Minion core to check for updates to the module and alert the user to install them as necessary.
To do this, the manifest included in the bundle must include the "X-Auto-Update-URL" property. This property should specify a URL where an XML file is located which indicates the update tree. For example, a manifest may include the following line:
Updates can be either critical or non-critical. Critical updates are required to be installed by the user. These types of updates should only be specified if failure to update will result in a failure of the system, such as when an API has incompatibly changed. For bug-fixes and feature improvements, non-critical updates should be specified. Non-critical updates alert the user to install updates when possible without impeding operation.
Updates also specify a "start" and "end" version which is targeted. Version numbers should be entirely numerical and separated with decimal points only. Update blocks will only be checked if the currently installed version is within the "start" and "end" version, inclusively. The "tag" version is the version number of the update.
All update XML files specify an UpdateData element with two attributes: bundleName and protocol. Currently, the only supported protocol is 1.0. This is provided for backwards compatibility in the event that the XML schema changes in the future. bundleName must be equal to the Bundle-Name property in the bundle's manifest. If it is not equivalent, a warning will be logged and the updates will not be processed, to avoid overwriting the module with an incorrect one.
A sample XML file for updating is shown below.
The schema for the auto-update XML is specified below. Please note this schema is subject to change.
|All times are GMT -6. The time now is 05:55 AM.|
vBulletin © 2013, Jelsoft Enterprises Ltd
©2012 ZAM Network LLC