| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> |
| <html> |
| <head> |
| <META http-equiv="Content-Type" content="text/html; charset=UTF-8"> |
| <title>The persistent cache under Apache Cocoon</title> |
| <link href="http://purl.org/DC/elements/1.0/" rel="schema.DC"> |
| <meta content="Gerhard Froehlich" name="DC.Creator"> |
| <meta content="This document explains how the persistent cache under |
| Cocoon operates." name="DC.Description"> |
| </head> |
| <body> |
| |
| <h1>Goal</h1> |
| |
| <p>This document explains how the persistent cache under |
| Cocoon operates.</p> |
| |
| |
| <h1>Normal filesystem persistence:</h1> |
| |
| <p>When you configure this opportunity, then the Cocoon objects will be ordinarily |
| serialized to a specified directory. This method is okay for a small number |
| of objects and if your OS can handle long filenames. Some Windows OS |
| have problems when the filenames are very long.</p> |
| |
| |
| <h1>Jisp based persistence:</h1> |
| |
| <p>The aim of the <a class="external" href="http://www.coyotegulch.com/jisp/index.html">Jisp |
| based</a> 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 need to handle many |
| objects.</p> |
| |
| |
| <h1>Configuration:</h1> |
| |
| <pre class="code"> |
| <persistent-store logger="core.store.persistent"> |
| <!-- Configuration goes here --> |
| </persistent-store> |
| </pre> |
| |
| <p>Please refer to <span class="codefrag">cocoon.xconf</span> file for further configuration |
| explanation.</p> |
| |
| |
| </body> |
| </html> |
