If your security scenario requires launching DI application from a webpage, then associating those applications with particular file extensions is required.
If the DI application is started with a filename, it looks to see if the file contains information on how to connect to DiveLine, and tries to do so if it does. The contents of the file should be a URI of the form:
protocol://username:password@server:port/path&name1=value1&...
all on one line, no terminating newline. The protocol is used to indicate which product should run.
Follow these conventions:
| Product | Extension | URI Protocol |
|---|---|---|
| ProDiver |
dlk |
prodiver |
| DI-Config | clk | di-config |
| DI-Controller | mcp | di-controller |
| ProDiveMaster | dmlk | prodivemaster |
|
|
wlk | workbench |
NOTE: The format and contents of a Workbench link file are not the same as the other link files. See Workbench Link File.