For the IIS website, everybody USES more, not verbose.
Today and talk about the difference between the "IIS application "and the virtualdirectorythat are less used by the group and the advanced application scenarios.
1: IIS website:Basic is a web site, a site, binding N a domain name, IP binding N, and then to set an application pool, basic ran up, and a web site can be innumerable applications and new virtual directory.The line is over, everybody knows, not to say.
2: application (independent development of the program under the same domain application strategy for independent deployment) :We found that under the IIS website, you can create a new "application", as shown below:
Here's an example of an application scenario:
Example 1: compare the usual site with the front desk and the backstage (the background of the system management site)
- Distribution of domain name:
And for the background, usually, we deploy the following domain name:
Basically not: admin888.cyqdata.com.
Most are: www.cyqdata.com/admin888.
Most of the reasons for adopting the latter are because cookies are good for the same domain, or for the same reason. - Deployment of IIS:
A: traditional way of deployment:
In the second way, if you don't know the application scenario, you might want to do the following deployment:
Publish the site to the root of www.cyqdata.com. The folder is called admin888 and follow the path.
This deployment, which is equal to development, is independent, and the final run is a site running, and, of course, modifying the background program, which also affects the foreground application.
B: application deployment:
If you see the second picture above, you can see three points:
1: alias: (equivalent to the directory name, then the access path becomes: http://www.xx.com/ alias)
2: application pool: you can run the application domain independently, and the program changes in the background will no longer affect the foreground.
3: physical path: you can put the background in any path instead of the root of the main station.
From these three points, it can be seen that the deployment of application mode is the way to recommend selection.
PS: in fact, by default the entire site is a default application.
Example 2: common site channels:
Such as:
http://www.cyqdata.com/news represents a news channel
http://www.cyqdata.com/sport represents a sports channel
There may be a variety of channels available at the end of the day and independently developed, and the power of the application deployed in the final deployment will come out.
3: virtual directory (one of distributed file storage schemes)
Brief description:
A virtual directory is a directory that can be mapped to any Shared directory on the network.
Virtual directory, in IIS6, looks like an application, as if it were a virtual path.
In fact, the effect of virtual directory is in the later distributed file storage:
Example 1: separate large amounts of static Html into a system disk:
If you need to generate a lot of HTML in your program, and in our program, the usual path is the root directory: "/ HTML /...
"
By setting the Html to a virtual directory, you can move the storage file to another disk.
Even if you want to delete it, just format it.
Assume that if your file is an Html folder directly under the root directory of your site, you will have a big head to delete.
Network node distribution, improve disk IO performance:
In addition to this mapping, you can also be mapped to different network hard disk, if you want to know the IO bottleneck, is the limit of single disk, by mapping to a different drive, improve the performance of point is: the limits of single disk * N disk.
The extension of all this is just a simple virtual directory mapping, moving the corresponding files, and the program does not need to move the knife, simply to complete the distributed storage of the file.
In this way, you can expand horizontally and continuously add separate hard drives to increase performance.
All right, that's it. Thanks for watching.