froehlich 02/03/14 13:43:00 Modified: src/documentation/xdocs/userdocs/concepts mrustore.xml book.xml Added: src/documentation/xdocs/userdocs/concepts persistence.xml Log: yo, new release is knocking on the door and this is great possibility to improve the user docs, hint hint! Revision Changes Path 1.4 +5 -5 xml-cocoon2/src/documentation/xdocs/userdocs/concepts/mrustore.xml Index: mrustore.xml =================================================================== RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/userdocs/concepts/mrustore.xml,v retrieving revision 1.3 retrieving revision 1.4 diff -u -r1.3 -r1.4 --- mrustore.xml 5 Feb 2002 01:46:44 -0000 1.3 +++ mrustore.xml 14 Mar 2002 21:43:00 -0000 1.4 @@ -51,17 +51,17 @@ <p> NOTE: The keys under Cocoon are Strings at the moment. Therefor the filenames of the swapped objects can be very long. Especially Windows OS - flavours have problems with long filenames. This problem is well known and - we are working on that. + flavours have problems with long filenames. Use the JispFilesystemStore to + get rid of it. </p> </s2> </s1> - <s1 title="Configuration of the MRUMemoryStore"> + <s1 title="Configuration of the MRUMemoryStore in the cocoon.xconf"> <source><![CDATA[ <store class="org.apache.cocoon.components.store.MRUMemoryStore" logger="core.store"> <parameter name="maxobjects" value="100"/> - <parameter name="filesystem" value="true"/> + <parameter name="use-persistent-cache" value="true"/> </store>]]> </source> <p>Explanation of the paramters:</p> @@ -70,7 +70,7 @@ Indicates how many objects will be hold in MRUMemoryStore. When the number of maxobjects has been reached, the last object in the MRUMemoryStore will be thrown out.</li> - <li><code><parameter name="filesystem" value="true"/></code>: + <li><code><parameter name="use-persistent-cache" value="true"/></code>: If this switch is set on true, objects are swapped out to the filesystem, if the MRUMemoryStore has reached his maximum object limit, or the JVM memory consumption is over the heap size limit. See StoreJanitor user 1.3 +1 -0 xml-cocoon2/src/documentation/xdocs/userdocs/concepts/book.xml Index: book.xml =================================================================== RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/userdocs/concepts/book.xml,v retrieving revision 1.2 retrieving revision 1.3 diff -u -r1.2 -r1.3 --- book.xml 20 Jan 2002 09:45:25 -0000 1.2 +++ book.xml 14 Mar 2002 21:43:00 -0000 1.3 @@ -19,6 +19,7 @@ <menu-item label="Matchers and Selectors" href="matchers_selectors.html"/> <menu-item label="Entity Catalogs" href="catalog.html"/> <menu-item label="MRUMemoryStore" href="mrustore.html"/> + <menu-item label="Persistence" href="persistence.html"/> <menu-item label="StoreJanitor" href="storejanitor.html"/> <menu-item label="XMLSearching" href="xmlsearching.html"/> </menu> 1.1 xml-cocoon2/src/documentation/xdocs/userdocs/concepts/persistence.xml Index: persistence.xml =================================================================== <?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="[EMAIL PROTECTED]"/> </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 class="org.apache.cocoon.components.store.FilesystemStore" 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>
---------------------------------------------------------------------- In case of troubles, e-mail: [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]