> > > From: > Matthew Toseland <toad at amphibian.dyndns.org> > Date: > Sat, 26 Oct 2002 14:21:25 +0100 > >> >>I know that there was a lot of talk about using HTL as a desision >>making mechanism for biasing the choice to cache data or to reset >>the datasource or not. Perhaps a more valuable use would be to >>have a little bit softer edge on the desision to queryreject or not. >> >> >We did this before, it didn't work. >
I think I remember what was done and the results were equivalent to the damping being too low resulting in limit overshoot and high resonace peaks. Not the sort of softening that I had in mind. >>If a request comes in with an HTL below some dynamic threshold >>based on the average HTLs of the other queries in the queue, then >>it is considered desperate and is handled. >> >> >No, we didn't do exactly that, preferring low HTLs is silly it > > >encourages bad behaviour. > When you have a minute (I realize that you are busy these days) could you elabourate on how encouraging low HTL requests in the network is silly. I would believe that the opposite is true and am curious what reasons you have to think the way you do. We already encourage lower HTLs by using the maxHTL setting in the configuration. > > >>This has the double benefit of virtually eliminating RNFs and >>encouraging using low HTLs (naturally discouraging high HTLs >>rather then having a hard cap on the max HTL) >> >>Just a thought, >> >>Mike >> >> >> >> > > _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
