So, it seems that in the SharePoint blogosphere, everyone is just copying and pasting the same markers from other blogs. One of the things I've seen is that SharePoint site templates are less efficient than site definitions because site definitions are stored on the file system. It's true?
It seems strange that site templates will be less effective. I understand that all site content lives in a database, regardless of whether you use a site template or site definition. The site template is applied once to the database, and from now on the site should not have problems if the content was created using the site template or not.
So, what is the architectural reason why a site template was less efficient than a site definition?
Edit: links to blogs that say there is a performance difference:
, , , , , , SharePoint.
, , .
.
?
, :
? , , "Ghosting" PAGE, SITE. , , , , .
. ? .
, : " SharePoint , ?" : " , , ". , .
"". , , yup, , . SharePoint, , , , , . , , , .
Ghosting 2003 (, STS , ), , " ".
, . "" - , , 2007 Masterpages .
- , .
SPS2003 . SharePoint 2007. -, SPVirtualPathProvider. , , .
un-ghosting ( , - , "un"?;-), , , , -, .. . - MOSS , , , , , , .
, , , , . , , , .
, .
Ghosting. SharePoint ( - pagelayouts) 12- - SharePoint. , SharePoint , .
, "Un-Ghost". , , SharePoint . "-" ( , ..). . 100 1000 , , .
, SharePoint - - ( ... ). , ( ) .
, . http://itfootprint.wordpress.com/2007/04/18/sharepoint-site-template-vs-site-definition/ http://my.advisor.com/doc/17614