Implement and document it this way. People using any current Frost
already have problems downloading CHKs that were inserted with a
filename. And because old Frosts always request a CHK without
filename, they will never get this new error code. They just get a
data not found from the node.

Once this is implemented I will change Frost so it always requests the
full chk/name key, and if the new error code 11 is returned then frost
strips the filename and keeps trying with the CHK only. This requires
some special handling for 0.7 (because Frost runs on 0.5 too), but its
easy to implement (I hope).

On 11/8/06, toad <toad at amphibian.dyndns.org> wrote:
> On Wed, Nov 08, 2006 at 08:55:20AM +0100, bbackde at googlemail.com wrote:
> > Hello,
> >
> > any progress on this item? I wait for a final implementation and
> > documentation. Then I can start to implement this.
>
> I have written some documentation:
>
> http://wiki.freenetproject.org/FreenetZeroPointSevenKeys
> http://wiki.freenetproject.org/SingleFileManifests
> http://wiki.freenetproject.org/FCP2p0ClientPut
>
> What you want me to implement:
> - If the node receives a request for a key with extra path elements, it
>   should return TOO_MANY_PATH_COMPONENTS (error code 11), with a URI
>   pointing to the same URI with the extra path elements stripped. In
>   fproxy this will be handled transparently as a 304 permanent redirect.
>
> Will this break lots of apps? Is it worth the disruption anyway? People
> running current Frost (20 june) will surely be affected by it.
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (GNU/Linux)
>
> iD8DBQFFUiaeA9rUluQ9pFARAkMnAKCmqFpdVJtVIbMQ8etWTNTAuWec/gCcCquj
> mZkR52rImCnIx38RyRq5n0Q=
> =qiwj
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> Tech mailing list
> Tech at freenetproject.org
> http://emu.freenetproject.org/cgi-bin/mailman/listinfo/tech
>
>

Reply via email to