In a content update, one or more AEM documents change. it effectively flags relevant pages as being out of date, without deleting anything. Auto-Invalidation automatically invalidates those parts of the cache that may be out of date after an update.Content Updates remove the pages that have changed, as well as files that are directly associated with them.The Dispatcher has two primary methods for updating the cache content when changes are made to the website. if you have an URL with a lot of selectors. There can be OS-level limitations for length of file name i.e.
The Dispatcher stores the cached document in a structure equal to the requested URL. The Dispatcher places the cached documents in the document root of the web server. The Cache Directory For caching, the Dispatcher module uses the web server’s ability to serve static content. However, the layout engine requires more processing power than a static server, so this setup may be prone to slowdown if many visitors use the system. This allows you to create richer, dynamic content, which increases the flexibility and functionality of your website. The engine reads content from a repository which, combined with styles, formats and access rights, transforms the content into a document that is tailored to the visitor’s needs and rights. If you use a Content Management Server, such as AEM, an advanced layout engine processes the request from a visitor.
Static web servers have been available for quite some time, so there is a wide range of tools for administration and security management, and they are very well integrated with network infrastructures. a HTML page), the file is usually taken directly from memory, at worst it is read from the local drive. This process is very simple, and thus extremely efficient. Static pages are created once, so the same content will be delivered for each request. Static Web ServerĪ static web server, such as Apache or IIS, serves static HTML files to visitors of your website.
This section illustrates the principles behind this. You can specify in detail which documents are stored as static files and which are always generated dynamically. The Dispatcher contains mechanisms to generate, and update, static HTML based on the content of the dynamic site. Static content is handled with exactly the same speed and ease as on a static web server additionally you can use the administration and security tools available for your static web server(s).ĭynamic content is generated as needed, without slowing the system down any more than absolutely necessary.
There are two basic approaches to web publishing: For details specific to this case see Using a Dispatcher with an Author Server, below. Most of the discussion focuses on this case.īut, the Dispatcher can also be used to increase the responsiveness of your author instance, particularly if you have a large number users editing and updating your website. The most common use of Dispatcher is to cache responses from an AEM publish instance, to increase the responsiveness and security of your externally facing published website.