On Mon, Dec 25, 2000 at 03:10:42AM -0600, Mark J. Roberts wrote:
> On Mon, 25 Dec 2000, Scott G. Miller wrote:
>
> > Keep thinking about it. If you combine SSK and map files (not
> > necessarily a hard and fast combination), you can keep the
> > implementation very simple by caching a mapfile in fproxy as an
> > association to the SSK parent key.
>
> The implementation is simple whether or not we restrict mapfiles to the
> SSK parent key. The advantage to your proposal is that we don't corrupt
> any of the other keytypes with ugly appendages. The disadvantage is that
> we would need to tell FProxy to use the mapfile, because it's not explicit
> in the URI. That would require a "Map=yes" attribute in the metadata of
> each file that contains any links, because the browser could begin at any
> file. That rules out cutting and pasting CHKs from other sources into your
> mapfile, at least CHKs that don't have the "Map=yes" attribute set. Once
> "Map=yes" is seen for a subspace, every request for data from that
> subspace is first checked against the mapfile, and if that fails, then it
> is requested normally.
No, you just have the metadata for each file have a pointer to the mapfile
to reference, as a Freenet key. And a construction guideline for
date-based enumeration.
>
PGP signature
