...
In a very basic setting the caching module can save local cache files based on every page request, for example every URL. But in several cases this may not really speed up the page because parts of the page might change often. Dynamic Content Overviews are an example of page sections that can change often.
In XperienCentral, page sections can be cached. This happens with Server Side Includes (SSIs). This is a common mechanism where tags are placed inside the (HTML/JSP) source code. These SSI tags refer to other pieces of code and can be referenced by local file path or URL. When the application server encounters an SSI tag it will request the SSI and add the generator code to the page. The following is an example of an SSI tag:
...
| Table | Description |
|---|---|
Tsdatabaseentitytimestamp
| Used for database detail pages. Timestamps are identified by the "dbid" parameter. |
Tsdatabasetimestamp
| Used for all databases. Timestamps are identified by the database ID. |
Tsdiscussiontimestamp
| Used for discussion timestamps. Timetamps are identified by the thread ID. |
Tsjellycontenttimestamp
| Used for Content Repository items. Timestamps are identified by media repository content ID. |
Tsjellyfishtimestamp
| Used for an Content Repository of a web initiative. Timestamps are identified by web initiative ID. |
Tsobjecttimestamp
| Used for various XperienCentral objects such as pages and page sections. Timestamps are identified by object ID. For pages this is also the ID in the URL of a page, for example |
tstermtimestamp | Used for Content Repository terms. When terms are changed they could influence content overviews so they have their own table. Timestamps are identified by term ID. |
...