ozeigermann 2003/12/02 08:04:45
Modified: src/doc stores.xml caching.xml
Log:
iso latin 15 broke the build
Revision Changes Path
1.2 +2 -2 jakarta-slide/src/doc/stores.xml
Index: stores.xml
===================================================================
RCS file: /home/cvs/jakarta-slide/src/doc/stores.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- stores.xml 2 Dec 2003 15:18:31 -0000 1.1
+++ stores.xml 2 Dec 2003 16:04:45 -0000 1.2
@@ -1,5 +1,5 @@
-<?xml version="1.0" encoding="ISO-8859-15"?>
-WORK IN PROCESS DO NOT TRANSFORM
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!-- WORK IN PROCESS DO NOT TRANSFORM -->
<document>
<properties>
1.2 +3 -3 jakarta-slide/src/doc/caching.xml
Index: caching.xml
===================================================================
RCS file: /home/cvs/jakarta-slide/src/doc/caching.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- caching.xml 2 Dec 2003 15:17:34 -0000 1.1
+++ caching.xml 2 Dec 2003 16:04:45 -0000 1.2
@@ -1,5 +1,5 @@
-<?xml version="1.0" encoding="ISO-8859-15"?>
-WORK IN PROCESS DO NOT TRANSFORM
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!-- WORK IN PROCESS DO NOT TRANSFORM -->
<document>
<properties>
@@ -55,7 +55,7 @@
to either be taken from this local cache or not at all from the cache, but
from the store. At commit time this
temporary data is atomically shifted to the main cache. Remember, there is
no need to update the store with
data from the cache as it always works in <em>write-through</em> manner.
All this guarantees the cache provides
- the isolation level <em><a
href="http://www.daffodildb.com/webhelp/Transaction_Support_&_Concurrency_Levels.htm";>read
committed</a></em>.
+ the isolation level <em><a
href="http://www.daffodildb.com/webhelp/Transaction_Support_&_Concurrency_Levels.htm";>read
committed</a></em>.
This is not that bad, but not that good as well. Unfortunately, there is no
obvious way how to achive this
without introducing locks to the cache. As the cache is not allowed to ever
block, a complicated invalidation
mechanism would have to be developed.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
