You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ojb-dev@db.apache.org by ar...@apache.org on 2004/01/04 19:33:39 UTC
cvs commit: db-ojb/xdocs objectcache.xml
arminw 2004/01/04 10:33:39
Modified: xdocs objectcache.xml
Log:
update cache documentation
Revision Changes Path
1.9 +12 -7 db-ojb/xdocs/objectcache.xml
Index: objectcache.xml
===================================================================
RCS file: /home/cvs/db-ojb/xdocs/objectcache.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- objectcache.xml 4 Jan 2004 02:34:37 -0000 1.8
+++ objectcache.xml 4 Jan 2004 18:33:39 -0000 1.9
@@ -198,7 +198,8 @@
Per default OJB use a shared reference based <code>ObjectCache</code>
implementation. It's a really fast cache but there are a few drawbacks.
There is no transaction isolation, when thread one modify an object,
-thread two will see the modification when lookup the same object.
+thread two will see the modification when lookup the same object or use a reference
+of the same object.
If you rollback/abort a transaction the corrupted objects will <b>not</b>
be removed from the cache (when using PB-api, top-level api may support
automatic cache synchronization). You have to do this using
@@ -210,7 +211,7 @@
ObjectCache cache = broker.serviceObjectCache();
cache.remove(oid);
</source>
-by your own.
+by your own or enable the <tt>useAutoSync</tt> property (more info see below).
</p>
<p>
This implementation use <code>SoftReference</code> to wrap
@@ -237,8 +238,11 @@
<tr>
<td>timeout</td>
<td>
- Lifetime of the cached objects in seconds.
- If expired, the cached object was discarded - default was 900 sec.
+ Lifetime of the cached objects in seconds.
+ If expired, the cached object was discarded - default was 900 sec.
+ When set to <tt>-1</tt> the lifetime of the cached object depends only on GC
+ and do never get timed out.
+
</td>
</tr>
<tr>
@@ -300,9 +304,10 @@
<b>ObjectCacheEmptyImpl</b><br/>
This is an 'empty' ObjectCache implementation.
Useful when caching was not desired.
-To support 'circular references' this implementation
-use a temporary map while store and delete operation
-(this may change in further versions).
+<br/>
+NOTE: This implementaion does not support <tt>circular References</tt>.
+Be careful when using this implementaion with references (this may change in
+further versions).
</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org
For additional commands, e-mail: ojb-dev-help@db.apache.org