Sharepoint

I got a chance to discuss some sharepoint things with my friends. I feel some of the points discussed are worth sharing.

Below are the points.

Difference Between Sharepoint and DotNetNuke:
· SP offers full-text indexing of the documents you store in it, and so you can search inside the documents in its libraries. DNN doesn't offer this.

· SP stores its documents very securely in the SQL database; DNN stores them as files, which means if someone knows the right path, the site's security could be bypassed and the documents downloaded directly.

· WSS was designed to integrate with Active Directory, DNN was designed to work with anonymous users and Forms Authentication.
· SP is basically used for Intranet applications. DNN is used basically for Extranet applications.

Ghosting:
Page ghosting, is a key factor in allowing a WSS farm to scale out to tens of thousands of pages across all the sites within a farm. Let me provide a quick example to
illustrate how page ghosting works.

Imagine that you have just created 100 new WSS sites from the Blank Site template. If none of these sites requires a customized version of its home page (default.aspx), would it still make sense to copy the exact same page definition file into the content database 100 times? The answer to this
question is obviously no. Fortunately, pages within a WSS site such as default.aspx are based on page templates that live on the file system of the front−end Web server. Page templates are used to provision page instances within the context of a site, such as the page that is accessible through a specific URL like http://litwareinc.com/default.aspx.

When a page instance is initially provisioned from a page template, WSS doesn’t need to store a copy of it in the content database because WSS can load the page template from the file system of the Web server and use it to process any request for an uncustomized page instance. Therefore, you can say that page ghosting describes the act of processing a request for an uncustomized page instance by using a page template loaded into memory from the file system of the front−end Web
server.

Page ghosting is valuable because it eliminates the need to transfer the contents of a page definition file from the SQL Server computer with the content database to the front−end Web server computer. Page ghosting also makes it possible to process the home pages for thousands of different sites by using a single page template that is compiled into an assembly DLL and loaded into memory in the IIS worker process just once per Web application. Both of these optimizations are key factors in the scalability of WSS in high−traffic environments running thousands or tens of thousands of sites.