diff options
author | Katharina Fey <kookie@spacekookie.de> | 2018-09-15 22:46:39 +0100 |
---|---|---|
committer | Katharina Fey <kookie@spacekookie.de> | 2018-09-15 22:58:19 +0100 |
commit | a0f9a5bb2a294674a28fc8ad38deb11d9bf9ecb1 (patch) | |
tree | 56ba7f22c2b7678a91b6b1bd8fc4d1184b1da69e /lockchain-files/src/load.rs | |
parent | ffafddfcbd07be8951701c3299407999928baddc (diff) |
A large batch of refactoring in FileVault
Okay what am I doing here? If you're reading this in the future,
it probably means I made some bad decisions. First: I'm sorry.
Secondly: let me explain why I did what I did...
Until this point `FileVault` has been a very transparent structure.
It didn't really interact with the data much, basically solving all
fs operations with streamed iterators and making sure stuff was done
correctly, but not adding any depth on top of that.
This needed to change...
This isn't quite done and most of the code just breaks here ;)
But the idea is to have `FileVault` be an intelligent wrapper around
the filesystem. That means that not only does it cache certain
operations for speed, it also keeps a selective index of files
that exist. So for example, `Headers` were added here, that are
always kept in sync with the FS. But only certain Records are stored
(not only for security but also size consearns).
After this refactoring is done (I shall write another long commit)
the FileVault will act more as it's own type than just a simple,
linear `Vault<T>` implementation.
Diffstat (limited to 'lockchain-files/src/load.rs')
-rw-r--r-- | lockchain-files/src/load.rs | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lockchain-files/src/load.rs b/lockchain-files/src/load.rs index fd4e66e..31da63c 100644 --- a/lockchain-files/src/load.rs +++ b/lockchain-files/src/load.rs @@ -7,7 +7,7 @@ use std::collections::HashMap; use ::FileVault; use ::config::{VaultConfig, ConfigError}; -use ::fs::{Filesystem, FileType}; +use ::fs::Filesystem; impl<T: Body> FileVault<T> { |