 |
|
 Topic  |
|
 Posted - Jun 29 2004 : 17:46:34
|
Used for online catalogues and shopping carts, Php, Cgi, Asp, etc, systems building pages on the fly from a database using templates for commonly used page layouts. Most 'out of the box' solutions include functions for image upload which require a gif/jpg image.
Changes needed to use Secure Image will be:
- the config script modified to allow the upload of .class files as well as jpg/gif
- the template presenting the image to include the applet code
- the database record for each item to include extra fields for the applet parameters
Customizing the html in the template pages will require basic html experience and some hours. So first consider which is the best system to use in your case.
A template needs to include the html for an applet code that can load its parameters from a database. The file size parameter is most important as it governs the scale at which the image is displayed. The file sizes can be entered manually, or they can be read in 'onLoad. With 'onLoad' there is a discrepancy between system size and the encrypted size so a few bytes need to be added (fileSize=imageSize+n).
With Secure Image and Copysafe, the image is displayed in an applet which is required on every page presenting an encrypted image. However Copysafe used in the header page alone, can protect any page that is included. This eliminates the need of reading in applet parameters and simplifies template
customization.
Changes needed to use Copysafe will be:
- add the code for small applet to the header and footer page templates
- no other modification required!
Further note:
- Secure Image 2.1 is not supported in Mac browsers
- Secure Image Pro is supported in all platforms
- Copysafe is supported in Windows and requires the visitor to download a
plug-in (similar to Flash)
. |
|
|
Topic |
|
|
|
|
Protecting Php, Cgi, Asp pages