diff options
author | Steve Slaven <bpk@hoopajoo.net> | 2009-08-04 21:31:17 (GMT) |
---|---|---|
committer | Steve Slaven <bpk@hoopajoo.net> | 2009-08-04 21:31:17 (GMT) |
commit | 09e55a6a1f9aeeccc8ae9e3b27850e40f7db7c2e (patch) | |
tree | 5e315294a4c5d5547def5c63ab5275645a4fa4b1 | |
parent | db8e7858692e9157b6dc9ac2471b62c40f5ff12f (diff) | |
download | fusearchive-09e55a6a1f9aeeccc8ae9e3b27850e40f7db7c2e.zip fusearchive-09e55a6a1f9aeeccc8ae9e3b27850e40f7db7c2e.tar.gz fusearchive-09e55a6a1f9aeeccc8ae9e3b27850e40f7db7c2e.tar.bz2 |
More thoughts/notes
-rw-r--r-- | README | 7 |
1 files changed, 7 insertions, 0 deletions
@@ -34,6 +34,13 @@ TODO: - should die on errors accessing blocks, will also need some kind of fsck to find corrupt blocks and files effected, this way if there is a problem and you have another copy of the file then the block can be recreated +- some kind of config/IOC to allow plugging in the hash, storage, etc + methods. Main components like FileSystem, Chunk, ChunkFile don't need to + be swapped out since they are generic +- Maybe compression method doesn't belong in Chunk? it should be part of + storage (for super-chunks?) or should super-chunks be a "standard" part +- Add refcounting so we can expire chunks, or would a reverse list be + better? ----- |