commit f4860799429aae0864ec62f3e0650486d02e3ce4 parent 6b88e3535a04e14a783684909280be8640603c1b Author: Siddharth Ravikumar <sravik@bgsu.edu> Date: Tue, 22 Mar 2016 10:58:37 -0400 update chapter 1, section 1.1. - Emphasize that combox does not use API provided by file storage providers to sync shards. Diffstat:
report/chapters/1-intr.tex | | | 8 | ++++---- |
report/combox-report.pdf | | | 0 |
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/report/chapters/1-intr.tex b/report/chapters/1-intr.tex @@ -77,10 +77,10 @@ across $N$ node directories; shards \verb+strunk-white.pdf.shard0+ to \label{fig:1-combox-overview-0} \end{figure} -combox does not sync encrypted shards stored in the node directories -to the respective file storage providers' data store. Instead, it -depends on the respective file storage provider's client program to -sync the shards. +combox does not use the API provided by the file storage providers to +sync encrypted shards stored in the node directories to the respective +file storage providers' data store. Instead, it depends on the +respective file storage provider's client program to sync the shards. combox can be used on all of the user's computers. For instance, the user can install combox on their second computer and combox will diff --git a/report/combox-report.pdf b/report/combox-report.pdf Binary files differ.