Start Components JAccelerator JAccelerator
 
|
| JAccelerator |
|
|
| Written by Administrator | |
 JAccelerator has unique capability to cache any modules and components with their individual time of existence in cache.Due to such mode of operation, the web page is built using blocks (components and modules) and we individually decide if they should be regenerated or retrieved from cache. How it works: - During the first retrieval of the page (with GET method) page display time is as fast as without 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 if certain module or component already exists in cache. - If it exists, the system displays it from cache without regeneration. - When the user is logged in, the system automatically erases data from cache no matter the time of their existence in cache is finished or not; that is why the changes are instantly visible and re-saved in cache. These are some of capabilities of the JAccelerator component: - very simple configuration; - very simple installation; - no need of 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; 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). Instalation In addition to standard installation, the component has executed new function during the process of installation: 1.a JAccelerator Plugin is installed; its publication or unpublication enables or disables the component to work. Besides plug-in enabling (which occurs automatically during installation), there is no need to publish the component and it is ready to use after configuration. General Guidelines 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. License GNU/GPL Special thanks - to Jacek Lipkowski (sq5bpf) for security audit; - to Magda Skarbek and Janeta Janicka for translation; |
|