Before talking about this technical problem, I can't help but think of a ridiculous story. Netcraft has made a assessment, this assessment based on the propeller of the proportion of website pages is ASP.NET or JSP / servlet, get a conclusion, now ASP.NET's application exceeds JSP / servlet. This assessment has triggered a lot of discussion, many of the technicians using JSP laugh at this assessment. Because this evaluation conclusion ignores a big problem. That is, the page of the website developed by JSP is. JSP? The answer is of course negative. In particular, the website of the MVC structure is often no .jsp extension, this is a practice. If not to avoid confusion, we can even let JSP engines to parse the JSP program named ASPX, or let the ASP.NET engine to parse the ASP.NET program named JSP. The only thing you need to do is to do some choices on the server's management tool, or modify the configuration file, etc. In addition, we can also use more powerful technology URLREWRITE to turn the address of the dynamic page as a static page, or turn the parameters of the dynamic page into a path name or file in a static page address, and the like. So, sometimes, please don't believe your eyes, as long as the server administrator wants to do it, then maybe a .htm address is actually an ASP.NET program, one .DOC is actually a JSP program. Seeing is not necessarily true.
