【正文】 英文翻譯 Cutting Edge A Clientside Environment for ASP Pages ASP is a Web technology that relies specifically on capabilities of Microsoft?Inter Information Services (IIS). For this reason, very few mercial products have attempted to provide an ASPtoHTML 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 doubleclick 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 doubleclick 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 ASPtoHTML 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 2020 Web Qamp。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 user39。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 it39。s requested, when a static HTML page would incur less overhead? An ASPtoHTML tool could be used as a kind of batch piler for ASP pages. You write them as serverside 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 I39。m on the subject, let me point out a significant improvement in the management of scriptless ASP pages that39。s available with IIS . Until IIS , all resources with a .asp extension were subject to parsing, whether or not they contained script code. With IIS this drawback has been eliminated as IIS checks for %...% blocks before loading the ASP parser. An ASPtoHTML converter would also be handy when you need to view ASP pages offline. For example, a client recently asked me about the possibility of using a single development environment for building both Web sites and CDs. I first considered using static HTML pages that could be viewed over the Web or in a local browser, but the idea was soon dismissed given the plexity and the amount of content involved. Also, my client could not guarantee any particular software configuration on the user39。s machine, and the only product that could be supplied with the CDs was Microsoft Inter Explorer or a custom Web browser. ASP looked like the natural choice for the Web side of the project, but what about the CD? To make ASP work offline without a Web server, you need code that extracts all the %161。 % code blocks from the page and processes them. In addition, this module would have to provide a simulated ASP object model and take care of collecting the portions of plain HTML text. Then it would have to put it all together, bining the static HTML code with the output of the processed scripts. In this column, I will discuss the architecture of the offline ASP viewer and some implementation details. In particular, I39。ll show you how to emulate the behavior of the ASP Response object. Next month, I39。ll finish up the code, covering Request and Server plus some other related topics. This month39。s code shows the potential of this approach and works with typical ASP pages, though it is not prehensive. I won39。t cover other ASP objects such as Session or Application because they are rarely needed in local scenarios. The Browser39。s Role To emulate ASP while working offline, you need a little help from the browser. Basically, the browser must be able to detect whether the page to which it39。s about to navigate is a URL or a local path name and whether it contains the .asp extension. If the user is calling a URL, the browser does what it would normally do. Otherwise, it calls a custom module to locally parse the content of the ASP file. Furthermore, the browser is involved when the ASP page that will be emulated contains forms and hyperlinks. (I39。ll discuss this further next month.) Given these requirements, to deal with ASP pages offline you need a customized version of the browser. While subclassing Inter Explorer or Netscape Communicator is always possible, I suggest you write a brand new browser from scratch using existing Web browser technology such as the Microsoft WebBrowser control. While I39。ll use Visual Basic?here, you can also use C++. As a good starting point in C++, you can try the MFCIE or ATLBrowser samples, both of which e with the latest Platform SDK. In Figure 1 you can see the layout of the browser. For illustration, I39。ve divided the client area into three blocks: one for the actual HTML rendering, one for the original ASP text, and one for the expanded HTML text. Figure 2 shows the code for the browser. Figure 1 The Custom ASP Browser?? During the form39。s initialization, a new CAspParser object is created and set to work properly. Once you39。ve clicked the Go button, the browser detects whether you39。re calling the ASP page locally or over HTTP, and acts accordingly. All the logic is hidden in the CAspParser class, which exposes three public functions: Initialize, SetscriptControl, and ParseTextToFile. Initialize makes sure the scripting environment is properly initialized and ready to work. Through SetscriptControl, the class receives the working instance of the script environment (more on this later). ParseTe