Why do you also execute pipeline events when accessing a static page?

1. The dynamic page cache implemented by the application caches the html file generated by the dynamic file to the file server, and then the user requests the dynamic file, and the corresponding static cached html file is loaded directly from the file server and returned to the user, which mainly saves the execution time of the dynamic language and the database access time. However, the caching framework will be added.

Static is relative to "dynamic", and a static page doesn't matter if it's not dynamic. Dynamics, then, refers to the fact that ASP or something is declared on IIS where the more complex ISAPI is declared.

The stream content output by the system of the process to the front-end; Static means that the IIS directly takes out thehtml、.txt、.exe、.xlsx、.mp4 and so on suffix file content and direct.

output of those. Among them, those that conform to the HTML hypertext agreement and are the static content mentioned above can be called "static pages".

As a result, let's say you have an ISAPI registered with the IIS to handlehtml suffix, do you still call it a static page? It can be completely output.

Let's talk about what it means to be "static":

Static is relative to "dynamic", and a static page doesn't matter if it's not dynamic. Dynamics, then, refers to the fact that ASP or something is declared on IIS where the more complex ISAPI is declared.

The stream content output by the system of the process to the front-end; Static means that the IIS directly takes out thehtml、.txt、.exe、.xlsx、.mp4 and so on suffix file content and direct.

output of those. Among them, those that conform to the HTML hypertext agreement and are the static content mentioned above can be called "static pages".

As a result, let's say you have an ISAPI registered with the IIS to handlehtml suffix, do you still call it a static page? It can be completely output.

Let's talk about what it means to be "static":

Static is relative to "dynamic", and a static page doesn't matter if it doesn't have dynamic mergers. Dynamics, then, refers to the fact that ASP or something is declared on IIS where the more complex ISAPI is declared.

The stream content output by the system of the process to the front-end; Static means that the IIS directly takes out thehtml、.txt、.exe、.XLSX, Purity. MP4 and other suffix files dig into the content and directly.

output of those. Among them, those that conform to the HTML hypertext agreement and are the static content mentioned above can be called "static pages".

As a result, let's say you have an ISAPI registered with the IIS to handlehtml suffix, do you still call it a static page? It can be completely output.

Dynamic pages need to interact with the server, while static pages don't, so the access speed will be faster than that of dynamic pages.

It can also be understood as: one reads the database, and the other does not read (the database may be divided into XML or relational databases, etc.).

Dynamics take up more of your web cache and less of static.

Dynamic pages require a compilation process.

Uh, the question is like this. You didn't specify the subject of the "visit" action. In fact, the question is 01Why does the browser need a web server to access JSP?

02 The browser does not need a server to access static HTML pages, and the bytes can be through the file path? If you have a little knowledge of the HTTP protocol or computer networking, you won't have such a laughing question, but no dumb question (I recommend you check out the headfirst servlet & jsp book).

The answer is this: the HTTP protocol stipulates that the browser needs to be connected to the Internet, and then "download" the resource (such as a static HTML page) to the local in the form of a "data stream", a process called the request-response process; The browser then reads the local HTML file**, parses the resource in HTML format, and displays it through the GUI. So not only JSP but also any resources including html files, img files, js files, etc., are such a process.

As for you click on the html file on the computer, this is the browser's own expansion process, it simulates the process of opening the file as an http request, in fact, the browser can open any text file, including jsp--jsp source file itself is a text file, but the browser will parse it according to the html format standard, so the 02 problem should not be accessed, at most it is opened. As for 01, Tomcat is a servlet container, which can be considered a type of web server software, and JSP is compiled by Tomcat parsing (note that it is not parsed by the browser on the client) and runs on Tomcat.

In short: the browser needs a server program to access any resource, the browser is responsible for executing the request, and the server program is responsible for executing the response; The browser can open HTML files and JSP files, but this process is not called access.

The difference between a static page and a dynamic page.

1. The content of static pages is relatively stable, and the URL address is easier to be recognized by search engines than that of dynamic web pages, so it is generally recommended to use static web pages when conducting SEO optimization.

2. Static pages do not need the support of databases, so the access speed is faster than that of dynamic web pages, but with the improvement of browser and broadband speed, this difference will become smaller and smaller.

3. Although static pages do not need to access the database, which relieves the pressure on the server, with more and more content, it will occupy more and more space on the server, and dynamic web pages have higher performance requirements for the server. In general, static web pages are suitable for less updated ** and are generally suitable for display **, while dynamic pages are more updated and generally used for ** with more user interaction.

2. The dynamic page is not a web page that exists independently on the server, when the user sends a request, the server may have to piece together other elements to return a complete web page, and once the static page is uploaded to the server, it is a web page file that is actually saved on the server.

Features of Dynamic Web Pages:

2. The dynamic web page is based on database technology, which can greatly reduce the workload of maintenance;

3. "?" in the dynamic web page"There are certain problems with search engine retrieval, and it is generally impossible for search engines to access all web pages from a ** database, or for technical reasons, search spiders do not crawl **"?"The content behind it, so the use of dynamic web pages in the search engine promotion needs to do a certain amount of technical processing to meet the requirements of the search engine;

4. Dynamic web pages are not actually web page files that exist independently on the server, and the server will only return a complete web page when requested by the user.

Features of Static Web Pages:

1. Static web pages are based on. htm、.html、.shtml、.xml, etc. as a suffix;

3. The interactivity of static web pages is poor, and there are great restrictions in terms of functions;

4. Once the content of the web page is published to the server, regardless of whether the user accesses, the content of each static web page is saved on the server, that is to say, the static web page is a file that is actually saved on the server, and each web page is an independent file;

5. Static web pages do not have the support of databases, and the workload in the production and maintenance of the website is large, so it is difficult to rely on the production of static web pages when the amount of information is large.

The simplest and most direct judgment for dynamic and static web pages is to look at the suffix of **.

This is mainly done in the browser, i.e. in the user's computer or mobile phone.

The main difference is that the data ** is different, the static web page does not need to obtain the data through the server, all the data is written in the web page.

The dynamic page needs to obtain the data through the server, which can be the data given when the page is rendered, or the data obtained through AJAX after the page is rendered. Of course, it will have a corresponding backend, and the backend will definitely run on the server.

Of course, all the web pages you access through **, even if they are static, need to be returned from the server.

Nowadays, there are very few purely static web pages, and the data returned by the server is generally dynamically obtained.

In conclusion, you have to be clear:

What you see in the page is done in the browser.

1. The working principle of BAI for static web pages is as follows.

du: a, the user is browsing.

Enter the address you want to access in the DAO address bar of the DAO browser and press enter, triggered.

This browsing is a request.

b. The browser sends the request to the web server.

c. The web server accepts the request and determines whether it is an HTML file according to the suffix of the request file.

d. The web server reads the correct HTML file from the specified location or memory on the server's hard disk and sends it to the requesting browser.

The user's browser parses the HTML and displays it.

2. The working principle of dynamic web pages is as follows:

a. The server accepts the request.

b. The web server reads the dynamic web page file from the location or memory specified by the server's hard disk.

c. Execute the program of the web page file, and convert the dynamic web page containing the program ** into a standard static page (html).

d. The web server will send the generated static page ** to the request browser.