Tutorial

EzWeb Compiler Content Storage files

The HSP DLL can work with EzWeb Compiler files so you can store all of your HSP pages (and other content files) in a single file. Although using EzWeb Compiler files is not a requirement for HSP, you will almost certainly want to use them for deploying your HSP applications. EzWeb Compiler files are content storage files, that allow you to store multiple files within a file. You stuff all of your ASP/HTM/Graphic project files into a single file, which the HSP runtime DLL seamlessly reads to deliver the content to IE. With the built-in security features of EzWeb Compiler, you can actually prevent an HSP application from being run without a password or machine license (see the EzWeb Compiler page for a complete explanation). Or, by splitting your HSP pages into different EzWeb Compiler files, you could restrict access to some parts of an HSP application, while allowing access to others, depending of the part of your HSP program and the EzWeb Compiler file it is stored in. Additionally, your source code is securely encrypted in the EzWeb Compiler file so it is safe from being pirated.

Why use EzWeb Compiler files?

Storing your ASP, HTML and other content files in a single EzWeb Compiler file makes sense for several reasons. One very good reason is to protect your IP.  If you don't use EzWeb Compiler files, then all of your script, HTML and other content will be completely exposed. You might not want just anyone to be able to open any of your files and see your source code. Worse yet, they could delete one or more files, which could make it very hard to figure out which one was deleted if you needed to. Stuffing all of your files into a single storage file makes it impossible for end users to tamper with. And with the built-in EzWeb Compiler security features, you get these benefits:

• With HSP, you will be able to write sophisticated programs that may be proprietary in nature. Since script code isn't compiled, you need to be able to secure it so it isn't exposed. EzWeb Compiler files are encrypted giving you the security you need.
• You can apply a password to your EzWeb Compiler files so they can't be loaded (by the EzWeb Compiler Viewer) or executed by the HSP runtime without the password. This also prevents other people with the EzWeb Compiler product from opening your EzWeb Compiler files and thus gain access.
• And lastly, you can require a machine license in order for EzWeb Compiler Viewer or the HSP DLL to open and execute code in your EzWeb Compiler file.

These three levels of security provide you with everything you need to write interactive, secure programs that run right in IE or in IEX in your custom programs.

Conclusion

EzWeb Compiler content storage files are the ideal method of not only deploying your HSP applications in a single file, but also of securing your applications and source code. HSP uses EzWeb Compiler files seamlessly, providing you with a complete application programming system.