Matthew Toseland <[EMAIL PROTECTED]> writes: > Um, no. The only things that get deleted due to running out of space are > those with a dirID of 0x1, i.e. keys stored in the datastore. 0x101 and > 0x102 are used internally to represent the routing table, and they never > get deleted unless explicitly told to by higher level code (this is > handled automatically, but the result is the minimum store size).
And there is an interface that fproxy can use to fetch keys so they end up in the datastore with a specific dirID? Does the relevant interface even guarantee that a fetched key will be cached in the local store at all, or may it be tunneled as well? Note that I'm not talking about what the current implementation does, but what the interface contract says. > Just set the dirID to something other than 1, and it'll persist until > you delete it. Exposing this functionality will enable some nice features. But it'll also open a can of worms: access needs to be restricted; what if a client forgets to delete such a persistent key; ... -- Robbe
signature.ng
Description: PGP signature
