The standard naming convention of the SS param files is *.prm
There are 2 levels of SSP files. The first file which is always searched for must reside in the same directory as the Java classes, usually Webmaster18/Java/ , and is named "default.prm". It is not required to be present, but must be in that directory if it's to be used.
The second file is HTML specified, so it can have any name and be located in any directory, provided it's on the exact same server as the Java classes (the server name must be an exact match [Java security restriction]). It's specified in the HTML source using:
<PARAM NAME=ssp VALUE=[prm file]>
Note: This is the only tag that cannot be in either of the SSP files.
This file also does not have to be provided.
The order in which params are taken is as follows:
1st) HTML-specified prm file (using the "ssp" applet param)
3rd) PARAM tags in the HTML source
Therefore, even if the same params are provided in all three files, the HTML-specified prm file takes precedence over the default.prm file which takes precedence over the tags provided in the HTML.
If it is necessary to specify applet params without putting the param values in the HTML source, to hide a channel password for example, you may use up to 2 server side param files. These files must be on the same server as the client Java files. The first file, which must be named "default.prm", must reside in the same directory as the Java files. It will always be parsed if available. It is not required to be available. The "lock" and "backpack" applet params are only used if they are found in the "default.prm" file. The second file can be specified by the "ssp" applet param. The value of the "ssp" applet param is a full or relative URL to the file on the same server as the Java client files.
The format of the server-side param files is one param and value per line in the file:
Comments may be used if the line begins with a ;
; this is a comment