diff options
| author | Siddharth Ravikumar <sravik@bgsu.edu> | 2016-02-28 00:10:10 -0500 |
|---|---|---|
| committer | Siddharth Ravikumar <sravik@bgsu.edu> | 2016-02-28 00:10:10 -0500 |
| commit | 8a36caa65e79717f114568be6d8ba7a599f145ac (patch) | |
| tree | ce67d631c3d3ec44cb9ba0f2dbc7c8f1ca35f39d /report/chapters/3-arch-d.tex | |
| parent | 8d23218a585947d638c3409d20169d00b66ceb24 (diff) | |
Refs to commits, source -> footnotes.
Diffstat (limited to 'report/chapters/3-arch-d.tex')
| -rw-r--r-- | report/chapters/3-arch-d.tex | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/report/chapters/3-arch-d.tex b/report/chapters/3-arch-d.tex index 8350f63..98c739a 100644 --- a/report/chapters/3-arch-d.tex +++ b/report/chapters/3-arch-d.tex @@ -192,10 +192,10 @@ The database is a JSON file on the disk, stored by default at is the sole interface to read from and write to database. The database is primarily accessed and modified by the combox directory monitor (\verb+ComboxDirMonitor+) and the node directory monitor -(\verb+NodeDirMonitor+) through a shared Lock\cite{py:threading.Lock} -that ensures that only one entity\footnote{An entity can be the combox - directory monitor or one of the node directory monitors} can -access/modify the database at a time. +(\verb+NodeDirMonitor+) through a shared Lock that ensures that only +one entity\footnote{An entity can be the combox directory monitor or + one of the node directory monitors} can access/modify the database +at a time. Below is an illustration of the structure of the combox database: |