Individual keys vs keyURL. a comparison:

You can now reference your Clipstream™ Audio or Clipstream™ Video applets to a common codekey text document by implementing the KeyURL parameter in place of the key param. This document acts as one central location where you can keep all your codekeys and update new ones, particularly if you have separate licensing agreements and temporary campaigns. This is useful for two reasons:

You can reflect any changes in your codekeys in one location. If your licensing situation changes, all you have to do is change the content in your codekeys.txt file instead of hunting down all of your applets to change each codekey reference. If you add Clipstream products or plan limited campaigns using Clipstream, again you can edit your codekeys.txt rather than change codekeys everywhere you use them.

This is how it works.

Create the codekey text document
Create a txt document named something like codekeys.txt (you can name the txt file anything you want but it must be reflected in the KeyURL parameter value) and place it in a permanent folder on your remote site. In that txt document, paste all of your valid codekeys. Separate more than one codekey with a space or carriage return as below:

A7NT2CFT7J5F5R7VDA7WM A5NT2CFT8J5F5R7VDA7WM

You can comment your codekeys by typing # and commenting after. Whatever text comes after the # on that line will be ignored. See the example below:

A7NT2CFT7J5F5R7VDA7WM # codekey for clipstream.com

Upload this codekeys.txt file and make note of the URL.

Modifying applet code for KeyURL parameter
In your Clipstream™ Audio or Clipstream™ Video applet, now, create a new parameter called KeyURL. See the examples below:

<param name="KeyURL" value="http://www.your domain.com/codekeys.txt">

or, with the codebase statement in use:

codebase="http://www.your domain.com/" archive=...

<param name="KeyURL" value="codekeys.txt">

As you can see, the value of the KeyURL parameter identifies the location of the codekeys.txt. Just delete or comment out your old Key parameter.

***Note: As with all other elements within the applet, the codekeys file must exist on the same server as the videoclipstream.zip or audioclipstream.zip file. This is due to Java security.
If you stream from multiple domains, each domain needs its own codekeys.txt.

***Note: If you are using Clipstream's Piracy Protection Package the secure key(s) and the non-secure (regular) key(s) will need its own codekey text file. Secure keys start with the letter S, so a secured Clipstream Video key will read SV... and a secured Clipstream Audio key will read SA.....