Platform SDK: Broadcast Architecture |
The process of loading current information into the Guide database begins with the Loadstub component of Broadcast Architecture. This component calls a loader to load data into the database. Which loader to call is specified in the Loadstub arguments when Loadstub runs.
Typically, you set the Loadstub component as a task in the Task Scheduler. Making Loadstub a task allows the Program Guide data for the tuning space associated with the specified loader to be automatically updated at regular intervals. The task for a particular tuning space specifies that Loadstub should be run and provides the globally unique identifier (GUID) of the database loader DLL to use.
To update Program Guide data, the Task Scheduler runs the stub program (Loadstub.exe) at the time designated in the task. When Task Scheduler runs Loadstub, it passes the GUID of the appropriate loader DLL along with other command options. Loadstub reads values in the broadcast client's registry to identify the location and file name of the appropriate loader DLL, based on the GUID that Task Scheduler passed. Then Loadstub uses this location and file name to load and call the specified loader.
The following illustration shows how the operating system starts the loader DLL.
For details about the registry values that support tuning spaces and Guide database loaders, see Program Guide Registry Values. For more information on creating and using Guide database loaders, see Guide Database Loaders.