...
If you are dealing with a live server with a significant load you have to be a bit more careful with updating the timestamps. For this purpose "soft timestamping" is available. By setting a soft timestamp, a special entry with ID 0 is created in the "sw_object" table. When a visitor requests a page, the timestamp of this page is compared with the "0" object. If the timestamp is older, a request is sent to regenerate the page , but and at the same time the cached version of the page is returned to the visitor, therefore the visitor doesn’t have to wait until the page is generated but instead they will get the cached page. The next vistor visitor will get the regenerated page. To use soft timestamping you have to click the [Update timestamps] button next to "General timestamp".
When you launch a new website, you can initialize the caching module by clicking on the [Update timestamps] button next to the "Initialize caching" label. This will create a timestamp entry for each page.
...
| Table | Description |
|---|---|
| Used for database detail pages. Timestamps are identified by the "dbid" parameter. |
| Used for all databases. Timestamps are identified by the database ID. |
| Used for discussion timestamps. Timetamps are identified by the thread ID. |
| Used for Content Repository items. Timestamps are identified by media repository content ID. |
| Used for an the Content Repository items of a web initiative. Timestamps are identified by web initiative ID. |
| 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 |
| 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. |
...