I do think storing binary content keyed by hash is a good idea but I would rather implement reference counting
which was trigger maintained than do some complicated view
for garbage collection.
I think the idea that you could only upload a little bit
of a file by checking the hash on the beginning is a bad
idea. What if I have a large docbook document where I edit
the afterword, the beginning will match and the end will be different. And as Don mentioned, there is not a way without
changing AOLServer itself to stop an upload like that. The only way really to implement this is to provide client side
software which computes the hash on the whole document locally then only uploads if it's changed. Something like
that would be very nice especially in the context of something like photobook where you might want to sync your
local photo collection to the server periodically.
Oh, and I think we should call the modules to do all this "OpenrsyncACS" and "OpentorrentACS".
