need to change the "_ default.xml" configuration file once you need to change
the address of your imaging server.
Usually you don‘t need to create a configuration file for individual images, as you
can specify the image path or other unique parameters dynamically by HTTP
query.
8.10.6 Passing Parameters by HTTP Query
This method is recommended for parameters from databases, parameters
specific to a certain image or FSI Viewer instance, or parameters related to
user interaction. Using server side script or JavaScript you can build HTTP
queries to pass parameters to FSI Viewer dynamically.
If you want to display multiple images with minimal variations in the FSI Viewer
configuration, it is recommended to reuse the same FSI configuration file and
to provide varying parameters (like the path to the image itself) by HTTP query.
Try to provide only those parameters by HTTP query that don not apply to
multiple instances of FSI Viewer. Keep in mind that changing a single
configuration file for multiple images later on will be far less work compared to
editing multiple HTML codes later on.
Providing parameters by HTTP query
View 1:
<PARAM name="movie"
VALUE="fsi.swf?cfg=flowers&imagepath=rose.fpx">
View 2:
<PARAM name="movie"
VALUE="fsi.swf?cfg=flower&imagepath=rose.
fpx&NoNav=1">
8.10.7 Retrieving Parameters from Imaging Servers
FSI Viewer is capable of retrieving image specific parameters from FSI Server
dynamically. This way you do not need to define these parameters explicitly.
The list below shows some typical parameters that can be retrieved from FSI
Server automatically:
l
ImageWidth
8 FSI Viewer
NeptuneLabs - FSI Viewer
194
