以主机命名的网站集
TechNet上的一句话：
如果要在一个 Web 应用程序中创建多个根级别网站集，以主机命名的网站集则不失为一种选择。例如，托管组织的管理员使用以主机命名的网站集创建多个以域命名的网站。 创建以主机命名的网站集不需要什么特殊模式（如主机标头模式）。可以使用 Stsadm 命令行工具创建以主机命名的网站集。
使用以主机命名的网站集可以更好地控制 URL。但是，有利亦会有弊。对于以主机命名的网站集需要注意以下事项：
-
以主机命名的网站集只有通过默认区域才可用。配置为通过其他区域进行身份验证的用户帐户不能访问以主机命名的网站集。
-
备用访问映射功能不能用于以主机命名的网站集。备用访问映射功能支持外部 SSL 终止，这使得远程员工访问和合作伙伴访问可以使用 SSL (HTTPS)。
容量
在一个 IIS 网站中最多可以创建 100,000 个以主机命名的网站集。
英文的：
Host-named site collections are an option if you want to create multiple root-level site collections within a Web application. For example, administrators for hosting organizations use host-named site collections to create multiple domain-named sites.
There is no special mode, such as host header mode, that is required to create host-named site collections. You create host-named site collections by using the Stsadm command-line tool.
Host-named site collections give you more control over URLs. However, there are tradeoffs. The following caveats apply to host-named site collections:
-
Host-named site collections are only available through the Default zone. User accounts that are configured to authenticate through other zones cannot access host-named site collections.
-
The alternate access mapping feature does not work with host-named site collections. The alternate access mapping feature provides support for off-box termination of SSL, which enables the remote employee access and partner access scenarios to use SSL (HTTPS).
没有明白什么叫“主机命名网站集”，从网上找一下：
You can create host named site collections if you would like to host all of your portal sites as site collections within one SharePoint web application.
· provide a fully qualified domain name (FQDN) for your SharePoint web application through the alternate access mapping in SharePoint Central Admin (Make sure DNS entry or host file entry made to resolve, leave host header blank at IIS site level)
· Create Site Collection using “stsadm” utility instead of central admin application and use the “–hostheaderwebapplicationurl” switch. This will create the site collection as host named site collection
Advantage of doing this would be you don’t have to manage too many content databases, IIS web sites etc. Probably not a good approach if you want to isolate content within site collections in separate content databases.
－－－－－－－－－－－－－－－－－－－－－－－－－－－－
MOSS Path-Based Sites vs. Host-Named Site Collections
There are many issues and considerations involved in developing a SharePoint site. You could probably spend an entire week reviewing all the design topics and checklists provided by Microsoft so I’m not going to try to write a simple blog on how to design your SharePoint taxonomy. What I did think was important was deciding between whether to use path-based sites or host-named site collections.
Path-based sites are created using Central Administration and are considered the traditional sites that you create. With path-based sites, you are limited to a single root-level site collection within a Web application, but the managed paths option allows you to create “top-level” sites beneath the initial root-level site collection. The major advantage of path-based sites is that these sites can be accessed from any zone that you configure. Also, the alternate access mappings feature, which provides support for SSL, works with all path-based sites.
Host-named site collections allow you to create many root-level host-named sites within a single Web application and are created using the stsadm command-line tool. They give you more control over URLs but not without tradeoffs. First, host-named sites are only available through the default zone and the alternate access mappings feature does not work.
