- Windows SharePoint Services is a site-provisioning engine, which makes it very easy for those with appropriate permissions to create new sites. In addition, the architecture is set up to support hundreds, thousands, tens of thousands, even hundreds of thousands of sites. If each site that was created resulted in a new Web root created on the file system, an organization of any size would quickly accumulate a large number of unmanageable Web roots on the server.
- consider a load-balanced environment. In a load-balanced environment, each SharePoint front-end Web server is essentially a mirror of other front-end Web servers. This means if an organization has hundreds of sites, they also have hundreds of Web roots, not to mention all the supporting files and assemblies for the site, on each server. This type of implementation would be very vulnerable to becoming out of sync with other servers or experiencing file corruption.
4. How many types of pages are in Sharepoint?
There are two types of pages are site pages (also known as content pages) and application pages. Site pages are the ones stored as instances in the site collection's content database. These pages fall into one of two categories: customized files or uncustomized files.
5.Uncustomized Files: When you create a new SharePoint site in a site collection, anywhere in a site collection, Windows SharePoint Services provisions instances of files into the content database that resides on the file system. The files on the file system are called templates. On their own they are not very useful because they cannot be accessed by using a browser. This is because they are not mapped to any specific URL. The instance of the file in the content database merely adds it to the site. When ASP.NET receives a request for the file, it first finds the file in the content database. This entry in the content database tells ASP.NET that the file is actually based on a file on the file system and therefore, ASP.NET retrieves the source of the file on the file system when it constructs the page.
This is how most files start in a SharePoint site. They are called uncustomized files. In the earlier version of SharePoint products and technologies (Windows SharePoint Services 2.0 and SharePoint Portal Server 2003) these files were called ghosted files, a term which has been deprecated. An uncustomized file is one in which the source of the file lives on the file system and not in the content database. The only thing that lives in the content database is the uncustomized instance that registers the file in the site.
One thing to note is that there can be multiple instances of a file in a site collection's content database, or content databases, all referencing the same file. This is how the out-of-the-box master page, default.master, is implemented. Every SharePoint site starts with an uncustomized instance of the default.master page. If an environment contained 100 SharePoint sites created with the Blank Site template, and no customizations had been made, there will be 100 uncustomized instances of the default.master page in the various content databases, yet there would be only a single default.master page on the file system.
6.Customized: A customized file is one in which the source of the file lives exclusively in the site collection's content database. In earlier versions (Windows SharePoint Services 2.0 and SharePoint Portal Server 2003) these files were called unghosted files, a term which has been deprecated. How can a file become customized? If you modify the file in any way through the SharePoint API, the source of the new page is saved in the content database. This includes SharePoint Designer 2007, which uses the SharePoint API via RPC and Web service calls to change files in sites. When the file is requested, ASP.NET first finds the file in the content database. The entry in the database tells ASP.NET whether the file is customized or uncustomized. If it is customized, it contains the source of the file, which is used by ASP.NET in the page contraction phase.
A file can start as an uncustomized instance and become customized. For example, after a site has been created, someone can open the site in SharePoint Designer 2007 and make a few changes to the default.master page for the site. When the file is saved, it has changed from being uncustomized to being customized. This enables Windows SharePoint Services to store only one instance of a file template on the file system regardless of how many sites implement it, while at the same time providing for site-by-site customizations of the file. Even if the file is customized, you can delete the customizations and put the file back into an uncustomized state by either right-clicking it in SharePoint Designer and selecting "Reset to Site Definition" .
7.Site Pages:Site pages are the ASP.NET 2.0 pages.These are the pages that support customization in the sense that they can be themed and they can host Web Parts.site owners and designers can customize these Site pages by using tools such as SharePoint Designer 2007. Site pages are virtualized in the site collection's content database.
8. Application Pages:application pages are much more like traditional ASP.NET 2.0 pages. These pages reside in a special virtual directory (http://www.localhost.com/_layouts/*.*) that all sites have access to. This virtual directory points to the [..]\12\TEMPLATE\LAYOUTS folder on the file system. All Windows SharePoint Services sites on a front-end Web server use the same pages. These pages are not provisioned as instances in the site collection's content database. Instead, they act just like traditional ASP.NET 2.0 pages. Each is coded to analyze the current context of the HTTP request such as which site collection, site, and user to determine what it should and should not do. These pages do not appear in SharePoint Designer 2007 when you browse a site because they exist only on the file system. Therefore you cannot customize them.
0 comments:
Post a Comment