Asp. NET pseudo static knowledge and how to configure ASP.net pseudo static

One, what is pseudo static

Definition: Dynamic Web pages by rewriting the URL method to remove the parameters of Dynamic Web pages, but in the actual page directory does not need to implement the existence of overridden pages.

For example: When we visit address http://www.cnblogs.com/ForEvErNoME/archive/2012/06/05/2529259.html, you Think that there is a 2529259.html file under the site server, in fact it may not exist, and you may see the content is through redirect/archive/article.aspx?year=2012&month=06&day =05&id=2529259 show it.

Two, why should the website pseudo static

1, pseudo-static use

Some users feel that the pseudo static and true static actual content will vary greatly, but in fact, from your personal point of view, you judge a post in the end is really static or pseudo static? It is difficult to see, because the so-called static meaning, is the address without a question mark, without a question mark is static, whether he is true or false? Does the search engine see it? So, in fact, whether it is true or false, in fact, for search engines are the same, the search engine did not say, you this is false, I do not include you.

To get to the bottom of it, why does the search engine not include the URL with question mark? Because the search engine is afraid because of the question mark to enter the dead cycle, called "Search Robot Trap (spidertraps)" (formerly mobile nets have such a loophole, spiders go out of the way), so many times with the address question mark search engine is not going in, pseudo static for search engines, in fact, is static Because there is no question mark in the address, so there is no real static than pseudo static more than the argument.

2, why choose Pseudo static?

A lot of users say: "Really static bad?" Why not really static? Isn't it quicker to visit? Isn't the load better? Wait a minute ...

Here, in fact, only one question to answer: Why Choose MySQL? Many users probably do not understand why so many large forums have chosen the MySQL database as a storage mechanism, probably most of them are thinking: "Because DZ used MySQL, so is MySQL."

In fact, imagine why DZ in so many forum programs coexist in the day to survive and laugh, a big reason is because DZ used MYSQL. Imagine if the Big C the program is a text forum, that there will be dz today? Or from another point of view, why do so many large Web sites have opted for MySQL rather than text as a storage mechanism?

The so-called text forum, actually with the true static argument almost, the data stored in the space above, a lot of read and written hard disk, etc. ...

Why would this writing be eliminated? I believe the answer will not be the teacher said: "Discuz! currently has 2,129,867 posts, stored into HTML is about 20799M, that is, 20G or so." This does not calculate the amount of space wasted by disk storage (100 1k of files may be 200K). "

This argument from my own point of view, this reason can not give the user not to use the real static sufficient reason. However, another reason is worthy of our attention, but also why most stations do not choose to generate static:

"Deleting and updating these HTML content can result in a lot of disk IO operations and a large amount of disk fragmentation." "

As mentioned above, in practice it does lead to a large number of disk I/O operations (input/output), the consequences of a large number of I/O operations can be imagined, resulting in a large number of disk fragmentation can even cause the hard drive to appear bad.

So for the generation of static, it would be better to use a text forum, you can more than solve your needs. (Vice W is to do text forum was born, when the name for Ofstar, after the development of the difficulties into MySQL, and PW generated static page is PW previous text way slightly improved to attract users eyeball of the pout)

Of course, if everyone has a good memory, should be able to remember when the PW4 PW Forum can not visit for a long time, and then recovered to a period of time before the data, the official saying is that people attack the hard disk damage, in fact, this argument is relatively unreliable, relative to be attacked resulting in hard disk damage or a large number of i/ O operation of the consequences, I personally more inclined to the latter.

Of course, if you are more concerned about 5d6d, you should know that a few days a day before 5d6d inaccessible, according to unofficial news because the hard drive is broken, and the cause of the damage I think of course because a large number of users I/O operations, imagine, we have a forum for disk I/O operations Only for administrators to update the cache, and 5d6d each member is an administrator, imagine the disk is how much test? So I'm not surprised 5D6D's hard drive is broken.

Of course, perhaps in reading this article many friends have used BT, also heard that BT on the hard disk is very hurt, can not open much, and the so-called damage, and here refers to the same thing, a large number of I/O caused disk fragmentation or even disk bad way.

Here are a few practical examples to illustrate the problem.

3. The disadvantage of pseudo-static

Of course, as the author of an article says: "If the traffic is slightly larger some use pseudo static CPU overload, I also online more than 300 people hang, and not use pseudo static when the online Super 500 people do not hang, my ISS number is 1000.

It is true that, because the pseudo static is to use the regular judgement rather than the real address, to identify which page is the responsibility of the direct designated by the CPU to judge, so the increase in CPU occupancy, is indeed the biggest fault of pseudo static.