DEPRECATION WARNING
This documentation is not using the current rendering mechanism and is probably outdated. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.
COA_GO¶
| Author: | Kasper Skårhøj |
|---|---|
| Created: | 2002-11-01T00:32:00 |
| Changed: | 2009-04-27T16:44:13.460000000 |
| Author: | Krystian Szymukowicz |
| Email: | typo3@prolabium.com |
| Info 3: | |
| Info 4: |
COA_GO¶
Extension Key: coago
Copyright 2008, Krystian Szymukowicz, <typo3@prolabium.com>
This document is published under the Open Content License
available from http://www.opencontent.org/opl.shtml
The content of this document is related to TYPO3
- a GNU/GPL CMS/Framework available from www.typo3.com
What does it do and why should I use it?¶
This extension improves caching of content object in TYPO3. It can decrease time rendering of page and increase overall performance of your site.
COA_GO fills the gap between full cached COA and COA_INT that is rendered each time the page is delivered to users browser. COA_GO renders its content only once and then if TYPO3 requests COA_GO again the content is fetched from cache (db, file, file with ajax) each time unless the cache period expires.
COA_GO can increase performance of your site in case of content elements that are the same at many pages. For example:
- any LATEST views that are put together with SINGLE,
- menus that are the same no matter at which page you are. (take under consideration that using javascript you can easily simulate ACT, CUR states),
- footers and tools menu which are rather the same at each page,
- search form putted at every page,
- logo with link,
- some banners repeated at every page.
Full documentation at TYPO3 Forge
http://forge.typo3.org/wiki/extension-coago/Documentation
COA_GO - 2