Static page conversion platform (STATICPOL)-Final Solution for static page generation

Why would you want to generate a static page?

This question we do not say more, his advantages only one, greatly improve the performance of the site, for large data volume, visit a large number of sites do not use static page output solution, I am afraid it is unbearable. The disadvantage is not to say, a lot of .... But the single advantage is worth studying. Let's discuss the general processing of the static page generation scheme and the Staticpol flexible approach to compare them.

Said he was a platform for the reason:

Normal way: In each program for static page generation to write the corresponding module (program), the implementation of the corresponding updates, and generally are manually updated (first page, category page, Information page), good trouble, even if it is scheduled to update, but also to write the appropriate procedures to implement.

Staticpol: Although he runs independently under the ASP.net, but can provide the corresponding static page generation service for the ASP, PHP, asp.net, JSP and so on any language program, provides the corresponding static page solution for it.

Said he was the ultimate solution for the reason:

Normal way: Either write the program batch update, or it is added, modified or deleted when the update. The former is not much said, simply a garbage treatment, but still a lot of people in use, the latter is better, but the program is very rigid, any configuration changes to involve the changes in the program.

Staticpol: Static page generation and updates occur when a user accesses it (the user does not access it and does not generate it. Because there is no sense in the generation, and the update of the page is controlled by the strategy, without the need for human participation, that is, you just define the update policy can be, the rest is by Staticpol To help you finish. User access generation can save a lot of IO operation resources, policy Management Update can achieve almost and dynamic management function synchronization realm, so I call the ultimate solution.

OK, let's start with a brief introduction to Staticpol's implementation principles:

Staticpol consists primarily of two ASPX files.

Index.aspx: Handles processing of 404 error pages.

Updatestaticfile.aspx: Used to implement policy updates to the generated pages.

Web.config: Storage System configuration information, static update policy information.

Here are some of the configuration information for my official station static update policy:

<!--

Static page Generation Policy

Makefilepath: Rules for static page addresses

LookFor: Rules for generating dynamic page addresses for this static page

Updatepolicy: The rules generated by this page

None: No action

Handwork: Manual (compared with system last update time)

Timespan: Time Lag