Two ways to generate static pages with PHP_PHP tutorial

1. When adding records in the management background, the target html page is directly generated, and the front-end call connection directly points to the generated html page. The advantage of this method is that the program is most efficient.

The server load is light, but since the generated page is purely static, once the page style (template and css=theme) is changed, all content pages must be regenerated.

Therefore, there are generally not too many applications in actual use. Most of them use client-side methods such as js, ssi, xml/xsl, etc. The generated static files only save data and do not involve styles,

This can achieve a balance between speed and maintainability, but it is more complicated than the front-end and back-end programs (when applying this method, since the content is purely static, it can be used with a separately compiled purely static apache. The efficiency and resource usage are higher than that of including Dynamic content support should be better)

====
Supplement:

a. To change the style mentioned above, to regenerate all content pages, you can pass:
>>>>You can embed a in each generated page to determine whether the page needs to be regenerated.

>>>>apache's ErrorDocument404 function, but the front-end link here points to html. If the html does not exist, the html will be regenerated through apache's function of redirecting to the 404 handler

(Note: httpd.conf plus ErrorDocument 404 /errprocess.php command), using this function can solve the problem of updating all generated html files when modifying the website style,

Just delete the entire static folder.

b. By embedding <script></script>js to call php, change many places that need to be changed (such as click-through rate, etc.)

2. The front-end access link points to the php program. The php program first checks whether the corresponding static file exists. If the static file does not exist. If so, it will be generated and redirected to this file, otherwise it will be redirected directly.

In actual use, this method is generally used together with the url_rewrite function of apache. Redisplay the php file address as html, which is beneficial to search engine retrieval.

This method has a slight loss in efficiency, but the program structure is simple and easy to adjust, so it is suitable when the number of visits is not very large.

Things to note:

All generated html files are placed in one folder. It should also be noted that if there are many generated files (such as forums), accessing one of the html files will become very slow,

Then it’s best to pass

>>>>Separate folders by date, such as static/2004/11/18/0001.htm
>>>> Make str_pad for the post ID based on the field length in the database: For example, if the ID is 123456 and it is int(11) in the database, then the ID processing is 00000123456. Considering that under Linux, the same file generally reaches four digits The data will have a performance impact. Cut it and the final path is static/00/000/123/456.html