[This is preliminary documentation and subject to change.]
The following outline is an example of a "typical" enhancement stream. The enhancement stream for a any particular show may vary. In the following, a typical enhancement stream is defined as a stream that is well-formed, and which contains one or more base pages.
The following topics describe the preceding steps in greater detail and provide example stream language statements for each step.
Announce the show repeatedly, either:
-00:30:00.00 announce "MyFuture.ann" repeat 180 until 00:00:00.00;
00:00:10.00 announce "MyCurrent.ann" repeat 180;
-00:30:00.00 announce "MyFuture.ann" repeat 180 until 00:00:00.00;
00:00:10.00 announce "MyCurrent.ann" repeat 180;
Trigger data reception repeatedly, by sending a Data trigger. This enables the client to receive enhancement files.
00:00:20.00 trigger (1 "<FTS> 125.354.23.11:190&MyShow") repeat 180;
Using the same repetition interval for both the announcement and data trigger keeps the two events consistently linked.
Transmit enhancement files repeatedly, using cabinet files to ensure that all dependencies arrive with the files. You can do this either by:
00:00:30.00 trigger(2 "<EnhPage.htm>") onefile repeat 270;
before 00:00:30.00-10 EnhCab.cab repeat 270;
00:00:30.00-5 trigger(1 "<CAB> [bpc://MyShow/EnhCab.cab]") repeat 270;
00:00:30.00 trigger(3 "<EnhPage.htm>") only repeat 270;
Send other triggers as needed throughout the show, repeating them as often as practical. Examples of additional triggers are: Nav triggers, script triggers, user triggers, etc.
00:01:00.00 trigger (4 "<JScript> alert(\'Thanks for tuning in!\')");
00:02:00.00 trigger ("3001 Q:What is the square root of 25?_A:5") repeat 30 until 00:10:05.00;
00:03:00.0 trigger(3 "<MyLeftPage.htm>[targ:LeftSide]") onefile repeat 90;