| <?xml version="1.0" encoding="UTF-8"?> |
| <!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.0//EN" "../../dtd/document-v10.dtd"> |
| |
| <document> |
| <header> |
| <title>The persistent cache under Apache Cocoon</title> |
| <version></version> |
| <type>Technical document</type> |
| <authors><person name="Gerhard Froehlich" email="g-froehlich@gmx.de"/> |
| </authors> |
| <abstract>This document explains how the persistent cache under |
| Cocoon executes.</abstract> |
| </header> |
| <body> |
| <s1 title="Goal"> |
| <p>This document explains how the persistent cache under |
| Cocoon executes.</p> |
| </s1> |
| <s1 title="Normal filesystem persistence:"> |
| <p>When you configured this opportunity, then the Cocoon objects will be ordinary |
| serialized to a specified directory. This method is ok when the amount |
| of objects are less and your OS can handle long filenames. Some Windows OS |
| have problems when the filenames are very long.</p> |
| </s1> |
| <s1 title="Jisp based persistence:"> |
| <p>The aim of the <link href="http://www.coyotegulch.com/jisp/index.html">Jisp |
| based</link> persistence is to provide a more scalable persistence. The objects |
| are stored in an indexed file, which uses a B-Tree alghorithm to store the objects. |
| This is a more elegant and fast solution, especially when you have to handle many |
| objects.</p> |
| </s1> |
| <s1 title="Configuration:"> |
| <source><![CDATA[ |
| <cache-persistent logger="core.store.persistent"> |
| <!-- Configuratin goes here --> |
| </cache-persistent>]]> |
| </source> |
| <p>Please refer to <code>cocoon.xconf</code> file how to configure this section.</p> |
| </s1> |
| </body> |
| </document> |
