On Wed, Mar 11, 2009 at 8:34 PM, Daniel Cheng <[email protected]> wrote: > You means insert those object as CHK@ ...? > > Then you have another set of problems: > 1) Some kind of pointer (be it SSK@, KSK@ or metadata in some file) > must exist. The egit-freenet client *have* to know the hash for your > c...@.. > If the pointer (let's assume it is a SSK@) fall out from the network, > we need the private key owner to recover. > -- this is no better then the scheme i proposed. > 2) objects are always identical, but packs are not. > To generate exactly the same CHK@, we have to either keep all > object loose (lots of very small files, too slow), or come up with > a packing order / scheme (just plain impossible)
I had assumed there would be a SSK referenced manifest which list the objects in the repo by hash along with an identifier for the CHK of the pack that contains them. If the clients save this information and don't purge any of the original objects, any of them should be able to reconstruct the CHK packs and reinsert the complete repo if it happens to fall out of the network. Also, reinserting just the CHK packs does have a big advantage: When something is actively developed people will often pull the SSK index and any new CHK packs, but old packs may fall out of the network because no one requests them anymore, yet a new user needs them for their initial pull. _______________________________________________ Devl mailing list [email protected] http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
