课件：SS中的UI制定.ppt

THANK YOU SUCCESS * * 可编辑 * TIMING: 30 seconds System Overview Before embarking on the development architecture for SharePoint Products and Technologies we must recall that the system is composed of: Stateless Web Servers Clones Single IIS application No registry keys No local data Stateful Data Servers Partitioned by site collection All user, site, profile, config data Portal services Search, index, job * TIMING: 30 seconds Web Server Components This module focuses on the web server which leverages the use of: ISAPI Filter ISAPI Application ASP.NET Handler ASP.NET * TIMING: 30 seconds Internet Information Services Role As already mentioned, IIS acts as: HTTP Listener Domain, Port, IP Resolution Virtual servers Authentication Anonymous, NTLM, and/or Basic Application Pools Process Identity Process Isolation Application Recycling * TIMING: 30 seconds ISAPI Filter’s Role After authentication, the ISAPI Filter looks at the requested URL to determine whether the request is for a SharePoint managed path. There is an administrator controlled list of included and excluded paths (implicit and explicit) that the ISAPI Filter bases its decision on. Assuming the request is for a SharePoint managed path, the ISAPI Filter then passes the request either to the ASP.NET Handler of handles the request through a SharePoint ISAPI Extension call. * TIMING: 30 seconds Managed Paths The main function of managed paths are to define which URL namespaces are managed by Windows SharePoint Services. There is a list of excluded paths as well a included paths. * TIMING: 30 seconds ASP.NET Handler’s Role Windows SharePoint Services uses ASP.NET pages (Active Server Pages or ASPX pages) for forms and lists. These pages can be customized, and you can add additional ASP.NET pages to run custom solutions on top of Windows SharePoint Services . ASP.NET pages in the _layouts directory for a SharePoint site run in direct mode, which means they are allowed to run directly. The _layouts direct