JAccelerator has a unique capability to cache any modules and components with individual specification of their life time in cache. Due to such a mode of operation, the web page is built as if out of blocks (components and modules) and it can be individually decided whether they should be generated again or retrieved from cache. Below, there are some capabilities of the JAccelerator component: - very simple configuration; - very simple installation; - no need make any change in joomla core files; - support for sessions and multilanguage; - automatic self-clearing function; - possibility of counting the page visits and banner displays (due to individual caching of components and modules); - GZip compression support; - changes of templates without cache emptying; - max cache size limit; - show/hide page generation time; - 2 cache modes for modules (full cache or 1 view only) (new!); How it works: - During the first retrieval of the page (by means of GET method), the page display speed is as fast as without an installed component. During this activity, the system saves all the information about the modules and components. - During the second display of the page, the system checks whether a given module or component already exists in a cache. - If it exists, the system displays it from cache without a renew generation. - When the user is logged in, the system automatically erases data from cache, regardless of the fact, whether time of their existence in cache is finished or not; that is why the changes are instantly visible and re-saved in cache. The component has been tested with Joomla v. 1.0.11 and 1.0.12. It should also work with previous versions (from 1.0.3). In particular, it is recommended to cache components of the following types: - content - contacts - Web links - user profiles - galleries - site maps It is particularly recommended to cache modules of the following type: - menus; - RSS headers; - polls; - logins; It is not recommended to cache components of the following type: - forums - components with their own caches (such as eWeather) - news feeds, discussion lists - other components, which content changes automatically without the need to log in to a site; It is not recommended to cache modules of the following type: - news on forums; - random pictures, tips; - banners; - visitors' counters; - other modules which content is changed with every page reload; As the component works (especially at the beginning), memory is allocated on the hard drive, so it is recommended to actively monitor cache size until it is stabilized. The cache size depends on how long the information is to be stored in a cache, frequency cache cleaning and specific page design.