Difference between revisions of "Device configuration"
From A-SMIL.org
Line 3: | Line 3: | ||
== The updateSettings Task Schedule == | == The updateSettings Task Schedule == | ||
− | To initiate device configuration, the player must be issued a SMIL script with a TaskSchedule subscription (see [[maintenance tasks]]) in the head section. The subscription contains a URL that points to a <tt>taskSchedule.xml</tt> file that looks like the following: | + | To initiate device configuration, the player must be issued a SMIL script with a TaskSchedule subscription (see [[maintenance tasks]]) in the head section. The subscription contains a URL that points to a <tt>taskSchedule.xml</tt> file that looks like the following: |
<source lang="xml"> | <source lang="xml"> |
Revision as of 04:53, 30 August 2013
A-SMIL players can have their configurations set using maintenance tasks.
The updateSettings Task Schedule
To initiate device configuration, the player must be issued a SMIL script with a TaskSchedule subscription (see maintenance tasks) in the head section. The subscription contains a URL that points to a taskSchedule.xml file that looks like the following:
<taskSchedule xmlns="http://schemas.adfotain.org/adapi-1.0"> <timedTaskList at="0" abortOnError="false"> <updateSettings id="123"> <sourceURI>http://server/config.xml</sourceURI> <contentType>x-configuration/xml</contentType> <contentLength>12345</contentLength> <contentChecksum>A72f43a7e0a5507923653f9a70260E70</contentChecksum> <checksumMethod>MD5</checksumMethod> </updateSettings> </timedTaskList> </taskSchedule>
Here several lines need to have proper values filled.
- updateSettings id: the ID is used by the player to register if a particular task has already be applied. The player will not apply the task if its ID is the same as the one most recently applied. In other words, if you wish you re-apply a task, make sure you change its ID
- sourceURI: a URL that points to a configuration file
- contentLength: size of the configuration file in bytes
- contentChecksum: MD5 checksum of the configuration file