On Fri, Nov 18, 2005 at 09:52:18PM +0100, freenetwork at web.de wrote: > >So here are some possibilities: > > > >1. For the first say 3 hops, the data is routed as normal, but is not > >cached. This is determined by a flag on the request, which is randomly > >turned off with a probability of 33%. > > Uhm... isn't this against the goal to increase a data chunk's presence around > the keyspace it's supposed to be stored? If it isn't cached within the first > hops won't this extemely harm keyspace specialization? Or perhaps - am I way > off here?
First 3 hops on the way out, from the requestor (furthest from the key). Not on the way back, from the datasource (closest to the key) :) -- Matthew J Toseland - toad at amphibian.dyndns.org Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: Digital signature URL: <https://emu.freenetproject.org/pipermail/tech/attachments/20051118/60c1ecde/attachment.pgp>
