You are here: Administrators Reference > Site Administration > Static Content Generation > Static Site Architecture > Static Site Main Concepts > Static and Dynamic Sub-domains

 

Static and Dynamic Servers

Unlike other CMS packages, CommonSpot Static Content Generation was designed with the idea that sites large enough to benefit from a Content Management Solution would also host both static and dynamic components and would benefit from a solution incorporating support for both content types.

The CommonSpot implementation assumes that a site configured to generate static content will be served from two servers: one dedicated to static content (for example: www1.paperthin.com) and one to dynamic content (www.paperthin.com). The servers can be virtualized on a single physical server, or can reside on two separate machines. Depending on site needs, they can also be clustered to provide load balancing. There are no restrictions on server names as long as one name identifies the dynamic content server and another identifies the static content server.

The dynamic server must run CommonSpot on either the authoring server in a single-server configuration, or the read-only production server in a multi-server replication environment. The static server does not require CommonSpot or ColdFusion.

Any page configured as dynamic (either auto-detect dynamic, forced dynamic, or required dynamic) will be served via CommonSpot on the dynamic server. Any page configured as static (either auto-detect static or forced static) will be served from the static server.  See Static Site Definitions.

 

Related Links


You can download PDF versions of the Content Contributor's, Administrator's, and Elements Reference documents from the support section of paperthin.com (requires login).


For technical support:

http://www.paperthin.com/support/