文档介绍：英文翻译
Cutting Edge A Client-side Environment for ASP Pages
ASP is a Web technology that relies specifically on capabilities of Microsoft? Information
Services (IIS). For this reason, very mercial products have attempted to provide an ASP-to-HTML converter. The problem with such converters is that you must work in conjunction with the Web server to trigger the ASP parser and find the intrinsic objects available. When you double-click on an HTML page from the Explorer shell, you simply ask the browser to retrieve and render the source code of the file. However, when you double-click on an ASP file from Explorer, you cannot ask the browser to translate it into HTML.
Practical Reasons for an ASP Converter
OK, so an ASP-to-HTML converter might not be the tool that thousands of programmers dream of every night.
However, I can envision at least a couple of scenarios where such a tool would be very handy. The first
scenario was mentioned by Robert Hess in the April 2000 Web Q&A column. Suppose you have several pages that require some interaction with a database on a frequently visited Web site. Writing them as ASP pages looks like the perfect solution. However, if the database is not very volatile and the page output is not highly dependent on the user's input, you could easily resort to plain old HTML for better performance.
For example, a list of suppliers is probably the kind of data that you would update only a few times a
year. Why rebuild that list on the fly each time it's requested, when a static HTML page would incur less
overhead?
An ASP-to-HTML tool could be used as a kind of piler for ASP pages. You write them as server-side resources, and then when you realize they are not particularly dependent on runtime conditions, you can transform them into static HTML pages with either the .asp or .htm(1) extension.
While I'm on the subject, let me point out a significant improvement in the management of scriptless ASP pages that's available with IIS