*** empty log message ***

diff --git a/Robust/Transactions/Notes/sysgurantees.dvi b/Robust/Transactions/Notes/sysgurantees.dvi
index d71f729ef7f9dd48bd1ea492fcb216b54c211cff..777cab9529808c6e46daf608ff305f9f434f3b12 100644 (file)
Binary files a/Robust/Transactions/Notes/sysgurantees.dvi and b/Robust/Transactions/Notes/sysgurantees.dvi differ

diff --git a/Robust/Transactions/Notes/sysgurantees.tex b/Robust/Transactions/Notes/sysgurantees.tex
index 8547fa32f63b8f16669d7a88e971dfa196b3a630..6c840770db5651d11e8f0228d5677a5ebf886802 100644 (file)
--- a/Robust/Transactions/Notes/sysgurantees.tex
+++ b/Robust/Transactions/Notes/sysgurantees.tex
@@ -76,6 +76,8 @@ TransactioalFiles can be either created inside or outside $T$. The Transactional
 A Transactionalfile can be shared among any subset of the members of $T$. If shared, the offset is shared between these too. 
 
 \section{Implications for the System}
+
+\subsection{General Principles}
 Now, if $T_i$ and $T_j$ do not either modify the data the other one uses, according to Rule 4 both can commit. This means even if $T_i$ accesses $tr_k$ before $T_j$ does, but $T_j$ commits before $T_i$, given that $T_j$ has not modified the data in use by $T_i$, $T_i$ could still commit. \\
 
 
@@ -102,12 +104,14 @@ The seek operations seeks to an offste within the file descriptor regardless of
 
 Principle 3) 1- A read operation in $OP_{T_i}$ "uses" contents read and makes $T_i$ dependent on the file contents read.\\
 
-proof: Due to assumtion 1 and since the data read by this operation can be used for computation, in case the data read would change, the data and hence computations results would be different. According to Def 2 it uses the data\\
+proof: Due to assumption 1 and since the data read by this operation can be used for computation, in case the data read would change, the data and hence computations results would be different. According to Def 2 it uses the data\\
 
 Principle 4) 1- A write operation in $OP_{T_i}$ does not make $T_i$ dependent on file contents.\\   
 
 proof: The result of a write would always be the same contents thus, according to Def 2 does not count as using.\\
 
+\subsection{A Model for Offset and Data Dependeny for Operations}
+
 Assumption: Each operation has a offset status assioated with it. We call this operation.offsetstatus. Each operation has a data satus assosiated with it namely operation.datastatus\\
 
 Assumption:  An operation with Speculative offset means the offset that the operation would be perfomed at can be relocated in the commit instant. An operation with absolute offset means the value is absolute and does not depend on any other operation OR the operation only specifies a specific value for the offset for the next operation (i.e. seek). An operation with defenite offset means the offset value that operation has to be carried on from, can not be relocated, but still could have changed before commit instant by other committed transaction and not being valid at commit instant\\