그저 그런 널널 한 얘기 들 . ....... : ( 영문 ) Virtual directory 
 ( 영문 ) Virtual directory 홈피 제작 관련 지식 
 engjjang . egloos . com / 478811 
 A sub - directory of a web - site in IIS can be either a physical sub - directory , or it can be a Virtual Directory that is logically mapped to that location . It really should not matter whether the directory is a physical sub - directory or a Virtual Directory , just like the location of the web - root isn ' t exposed . In most production cases , especially with shared web - hosts , you will only be able to create physical sub - directories , probably using FTP or similar tools . 
 If you open up the Internet Services Manager in your Administrative Tools , also called IIS Manager , and drill down you will see the logical structures . Physical directories are shown with a folder icon , while Virtual Directories are shown with a special folder icon that has a globe as part of the icon . You may also see another icon , either a box around a globe icon ( Win 2 K / XP ) or a gear icon ( W 2003 ) , which indicates the directory is an IIS Application . 
 An IIS Application is a directory , physical or virtual , that has been setup in a manner that makes it logically independent from the rest of the web - site . Its purpose is basically to make sub - directories act just like real web - sites , which is very useful on Win 2 K / XP Pro , but not really necessary on a Server . Its important to understand that you cannot create an IIS Application simply using FTP or similar tools -- and this is the cause of many ASP . NET problems . 
 So how do you create an IIS Application ? First , VS . NET automatically makes all new web projects into IIS Applications , whether you want it to be or not . Otherwise , you need to use IIS Manager to create or setup an IIS Application , or get your web - host to do it for you ( WebHost 4 Life . com has a tool for this ) . The easiest technique is to use IIS Manager to create a new Virtual Directory -- it will also be an IIS Application by default , which adds to the confusion . 
 The alternative is much more revealing , so you really need to try it yourself . Using the IIS Manager , select any directory and then go to its property pages , then go to the Directory tab ( may be labeled Virtual Directory or Home Directory ) . The bottom half of this form will be labeled Application Settings and you will see either a Create or a Remove button -- if you see the Create button then it is not an IIS Application , if the Remove button then it is an IIS Application . 
 Notice that some of the other items are only available for IIS Applications : Application Name , Configuration , Application Protection , and possibly Unload . The Configuration button brings up a dialog to map file extensions to ASP . NET , or other processes , as well as options like session state enable and timeout . The Application Protection drop - down determines if this IIS Application is to be isolated in its own process , pooled with other apps , or in - process with IIS . 
 IIS Applications also have events that can be defined in a global . asa / asax file . Global . asa / asax events only get executed for IIS Applications , and only if the file is at the app - root -- note that " asa " stands for Active Server Application . IIS Applications start when the first page in them is requested , and continue to run until they are stopped , either manually with the Unload button , or due to timeouts or other constraints automatically applied in ASP . NET configuration . 
 Depending on an organization ' s needs - a virtual directory can complement or replace a metadirectory . 
 Most virtual directories act as proxies . The virtual directory sits between an application and a set of authoritative sources to create a view of a user , generally through the LDAP protocol . Virtual directories may create a user view by joining a user ' s identity data or by integrating directory information . Typically a virtual directory will integrate with other LDAP directories , relational databases and network operating system directories . 
 Potential advantages of virtual directories : 
 Faster deployment by avoiding synchronization 
 Leverage existing investments in security and high - availability for authoritative data stores 
 Provide application specific views of identity data which can help avoid the need to develop a master enterprise schema 
 Allow a single view of identity data without violating internal or external regulations governing identity data 
 Act as identity firewalls - preventing denial of service attacks on the primary data - stores and providing further security on access to sensitive data 
 Changes made in authoritative sources are reflected in real - time 
 Organizations that implement virtual directories need to be aware of the following potential deployment challenges : 
 Having the virtual directory implementation augment the high availability of authoritative sources 
 Meeting the latency and performance requirements which are dictated by the business requirements of the client applications 
 Some Typical Virtual Directory Terminology : 
 Mapping - The transformation of data inside of the virtual directory . For instance mapping uid to samaccountname . 
 Identity Routing - Virtual directories may support the routing of requests based on certain criteria ( such as write operations going to a master while read operations being forwarded to replicas ) . 
 Authoritative Source - A " virtualized " data repository , such as a directory or database , that the virtual directory can trust for user data . 
 Retrieved from " http : / / en . wikipedia . org / wiki / Virtual _ directory " 
 Virtual Directories ( IIS 6 . 0 ) 
 To publish from any directory not contained within your home directory , you must create a virtual directory . A virtual directory is an alias , either for a physical directory on your server hard disk that does not reside in the home directory or for the home directory on another computer . An alias is a name that Web browsers use to access the virtual directory . Because an alias is usually shorter than the path name of the directory , it is more convenient for users to type . A client simply adds the alias to the URL of the Web site to browse the Web content in that virtual directory . 
 Using virtual directories offers several benefits . Not only is an alias usually easier for users to type and remember , but also it is a good security practice to use virtual directories because an alias hides the physical location of your files from unauthorized users . In addition , virtual directories make it easier for you to change and manage the directories on your site . If you change the name or location of a directory , you can simply change the mapping between the alias and the physical directory , rather than change the URL of the Web site . 
 In addition , virtual directories allow administrators to store content in different locations . Users can access the directories using simple URLs . For example , if a default Web site is located at C : \ Inetpub \ WWWRoot , an administrator can create a virtual directory as a subdirectory of the default Web site , but the virtual directory can have a physical directory in a different location , such as D : \ Data . If the virtual directory has an alias of Data , and the server name is MyWeb , users can access the default Web site and the virtual directory by typing http : / / MyWeb and http : / / MyWeb / Data , respectively . 
 If you have a simple Web site housed on one directory , using virtual directories is an optional , although recommended , practice . However , if you have a complex site that spans multiple directories , drives , or computers , or if you want to specify different URLs for different parts of the site , you must use virtual directories . To set up a virtual directory that maps to a directory on another computer , you must specify the Universal Naming Convention ( UNC ) name of the directory and provide a user name and password . 
 For step - by - step instructions for creating and deleting virtual directories , see Using Virtual Directories . 
 다음 글 : ( 영문 ) Cool Graphic Resources on the Web 
 이전 글 : ( 영문 ) Understanding Paths