Commits

Anonymous committed bd843cf

Updated docs to reflect new changes and fixes.

Comments (0)

Files changed (2)

docs/changelog.html

 
 <body>
 
+<h3>OSCache 2.1</h3>
+<p><i>(26th September 2004 - by <a href="mailto:oscache at andresmarch dot com">Andres March</a>)</i></p>
+<b>Bug Fixes:</b>
+<ul>
+  <li>[<a href='http://jira.opensymphony.com/browse/CACHE-70'>CACHE-70</a>] - last modified problem</li>
+<li>[<a href='http://jira.opensymphony.com/browse/CACHE-73'>CACHE-73</a>] - NullpointerException after deserialization of AbstractConcurrentReadCache</li>
+<li>[<a href='http://jira.opensymphony.com/browse/CACHE-85'>CACHE-85</a>] - JavaGroups changed package name</li>
+<li>[<a href='http://jira.opensymphony.com/browse/CACHE-98'>CACHE-98</a>] - Disk cache not getting served first time for long keys</li>
+<li>[<a href='http://jira.opensymphony.com/browse/CACHE-107'>CACHE-107</a>] - flushEntry does not behave correctly in cluster</li>
+</ul>
+<b>Improvements:</b>
+<ul>
+  <li>Website documentation updates.</li>
+  <LI>Added HashDiskPersistenceListner that hashes file names in order to
+  eliminate nasty characters and overly long names</LI>
+  <LI>Added property that allows cache entries to only be persisted when 
+  the memory capacity has been exceeded.  The property is called: cache.persistence.overflow.only.
+  It defaults to false for backwards compatibility meaning all cache entries are persisted when
+  a listener has been registered.</LI>
+  <li>[<a href='http://jira.opensymphony.com/browse/CACHE-58'>CACHE-58</a>] - If-Modified-Since ignored in cache filter</li>
+<li>[<a href='http://jira.opensymphony.com/browse/CACHE-92'>CACHE-92</a>] - public access for configuration properties</li>
+<li>[<a href='http://jira.opensymphony.com/browse/CACHE-94'>CACHE-94</a>] - More evenly distributed disk caching</li>
+<li>[<a href='http://jira.opensymphony.com/browse/CACHE-95'>CACHE-95</a>] - Output the scope name's in toString()</li>
+<li>[<a href='http://jira.opensymphony.com/browse/CACHE-104'>CACHE-104</a>] - Destroy cache</li>
+<li>[<a href='http://jira.opensymphony.com/browse/CACHE-105'>CACHE-105</a>] - call get() method on put() method call</li>
+</ul>
+
 <h3>OSCache 2.0.2</h3>
 <p><i>(22nd January 2004 - by <a href="mailto:pathos at pandora dot be">Mathias Bogaert</a>)</i></p>
 <b>Bug Fixes:</b>

docs/configuration.html

 
 <h3>cache.unlimited.disk</h3>
 <p>Indicates whether the disk cache should be treated as unlimited or not. The default value is
-<code>false</code>.</p>
+<code>false</code>.  In this case, the disk cache capacity will be equal to the memory cache capacity set by
+cache.capacity.</p>
 
 <h3>cache.persistence.class</h3>
 <p>Specifies the class to use for persisting cache entries. This class must implement the <code>PersistenceListener</code>
 interface. OSCache comes with an implementation that provides filesystem based persistence. Set this property
-to <code>com.opensymphony.oscache.plugins.diskpersistence.DiskPersistenceListener</code> to enable this
-implementation. By specifying your own class here you should be able to persist cache data using say JDBC or LDAP.</p>
-<p>The <code>DiskPersistenceListener</code> class requires the following extra configuration property to be
+to <code>com.opensymphony.oscache.plugins.diskpersistence.HashDiskPersistenceListener</code> to enable this
+implementation. By specifying your own class here you should be able to persist cache data using say JDBC or LDAP.  
+NOTE: This class hashes the toString() of the object being cached to produce the file name of the entry.  If you
+prefer readable file names, the parent DIskPersistenceListener can still be used but it will have issues with illegal 
+filesystem characters or long names.</p>
+<p>The <code>HashDiskPersistenceListener</code> class requires the following extra configuration property to be
 set:
 <blockquote>
 <h3>cache.path</h3>
 <p><code>cache.path=/opt/myapp/cache</code></p>
 </blockquote>
 
-<h3>cache.persistence.overflow.only</h3>
+<h3><B>NEW! </B>cache.persistence.overflow.only</h3>
 <p>Indicates whether the persistence should only happen once the memory cache capacity has been reached. 
 The default value is <code>false</code> for backwards compatibility but the recommended value is 
-<CODE>true</CODE> when the memory cache is enabled.  This drastically changes the behavior of the cache in that 
-the persisted cache will now be different then what is in memory.</p>
+<CODE>true</CODE> when the memory cache is enabled.  This property drastically changes the behavior of the 
+cache in that the persisted cache will now be different then what is in memory.</p>
 
 <h3>cache.event.listeners</h3>
 <p>This takes a comma-delimited list of fully-qualified class names. Each class in the list <em>must</em>