Tyler Riddle <triddle_1999 at yahoo.com> writes:

> This is only a bad idea if you enjoy having RNF and
> DNF ruin your freenet using experience. I suggest you
> actualy try the patch and see how effective it is at
> pulling pages through that DNF at HTL 25 after 3 or 4
> attempts (just leave your page open over night and you
> run a good chance of having it waiting for you in the
> morning). 
> 
First, if your node is RNFing, retrying the request is among the last
things you want to do.  RNF can be a sign that your internet
connection is down (and your node can't contact any others to forward
requests to).  When this is the case, auto-requesting until you find a
key will not only never find the key, but it'll empty your routing
table as every node in it fails connection requirements time and
again.

If a page has DNFed at HTL=25 after 3 or 4 attempts, it should be
"not-retrievable", and given up on.  If the key is in freenet and
isn't being found, the solution is *not* to add a auto-retry "feature"
into fproxy; that's just patching over the symptom of the problem.
The real problem is that the key isn't being found, and it's this that
needs to be worked on, either by tweaking routing table settings so
that nodes (in general) use more information to route, or by making
requests more lightweight so that higher HTLs can be supported.


> Regarding the "flood the network" switch, we allready
> have frost which does a plenty good job of flooding
> the network. I'm no freenet expert but I suspect the
> ammount of trafic this will generate (one request
> every couple to 10 minutes at high HTL) is minimal
> compared to the load that frost places on the network.
> 
> Tyler

<SNIP>

Frost is *not* distributed as part of the node.  Yes, many people are
using frost to flood the network, but that doesn't mean we should make
people flood the network each time they browse to an edition-based
site.  Yes, I'm talking about the links to future editions, which will
set fproxy working forever trying to find data that's not in the
network.  As for your characterization of "one request ever couple to
10 minutes", I see that number easily becoming *much* larger after a
short amount of browsing.

Thelema
-- 
E-mail: thelema314 at swbell.net                         Raabu and Piisu
GPG 1024D/36352AAB fpr:756D F615 B4F3 BFFC 02C7  84B7 D8D7 6ECE 3635 2AAB

_______________________________________________
devl mailing list
devl at freenetproject.org
http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl

Reply via email to