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.

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.

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:

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

Ex.
In your Clipstream™ Video .js file create a new .csv parameter called KeyURL.

1. Open the.js file that contains the Clipstream™ Video code in a text editor.
   
2. Add a new csv line called KeyURL.
   
   Ex.
   csv.KeyURL ='[URL of codekeys text file here]' ;
   
3. Where [URL of codekeys text file here] replace with the URL address and text file name of the text file you just created. You can use relative or absolute links. If relative links are used they must be in relation to the clipstreamvideo.zip employed by the applet.
   
   Ex.
   // codekeys text file located in same folder as clipstreamvideo.zip
   csv.KeyURL ='codekeys.txt' ;
   
   -or-
   
   // codekeys text file located in license folder below clipstreamvideo.zip
   csv.KeyURL ='license/codekeys.txt' ;
   
   -or-
   
   // codekeys text file located at root of domain
   csv.KeyURL ='/codekeys.txt' ;
   
   -or-
   
   // codekeys text file identified as absolute link
   csv.KeyURL ='http://www.clipstream.com/codekeys.txt';



Note: the codekeys.txt must be on the same server as the videos. This is due to Java security.
If you stream from multiple domains, each domain needs its own codekeys.txt and of course your license must cover all of these domains.

If you are using Clipstream's Piracy Protection Package the secure key(s) and the non-secure (regular) key(s) will need their own separate codekey text file. Secured Clipstream Video keys will read start with the SV alphanumeric.