Changes

Jump to: navigation, search

Software Update:Checking For Updates

90 bytes added, 17:50, 28 April 2005
no edit summary
The Update Service:
- * checks for updates to the application on a background timer- * provides a means for the user to check for updates to the application- * provide a set of controls for determining update behavior
= The Update Check=
1. # generate update service URL2. # determine if updates are available3. # determine action4. # download patches5. # verify patches6. # install patches
The = Update Service URL=
- The Service URL needs to incorporate data in these dimensionsso as to reduce the complexity of the processing on the client side: - * app name - * app locale - * app version - * app buildid (for distinguishing between nightlies on a "tester" build stream for example) - * app buildtarget
e.g.
<tt>/firefox/1.0.3.20050414/i586-pc-msvc/en-US/update.xml</tt>
=The Updates File=
update.xml is an XML file that tells about available updates. It is formatted
like this:
<tt><pre>
<?xml version="1.0"?>
</update>
</updates>
</pre></tt>
The application should provide a preference setting that can be set to hold
The update.xml file for the 1.1.1 user might look something like this:
<tt><pre>
<?xml version="1.0"?>
</update>
</updates>
 
</pre></tt>
And for the 1.1.4 user like so:
<tt><pre>
<?xml version="1.0"?>
</update>
</updates>
 
</pre></tt>
So the user of 1.1.1 will have the 1.1.2, 1.1.3, and 1.1.4 patches
This implies that the database that manages all of this version information
has to know that some updates can only apply to certain version (ranges).
 
Extensions
* eventually move EM updating fully into EM
525
edits

Navigation menu