On Sun, Feb 17, 2002 at 01:46:46PM -0500, Gianni Johansson wrote: > Even if the data was written somewhere in the network, there is no guarantee > that it ended up in a place that makes sense routingwise. The network used > to be so small that this didn't matter. Now it does.
Yes, but if you are using the same references to route the request then it doesn't matter whether the insert went in a sensible direction, the request will go in the same direction. > > What realistic circumstance could result in the data > > not being found when the local data store is ignored after a successful > > insertion? > If it fell out of the network or landed in a ridiculous place routingwise. It is unlikely to fall out of the network in such a short space of time, and whether it is in a rediculous place routingwise won't make a difference if you are using the same set of references to route the request. > In a perfect world yes. We do not live in such a world. The routing is > suboptimal. The problem is that most useful nodes are overloaded. I don't disagree, but I don't see why this would have a significant effect if I insert some data, then request it shortly afterwards while ignoring my local cache - unless it just so happens that the node to which the insert was routed is rejecting queries. > Right now > my node is QueryRejecting all but ~=1500 of the 10000+ requests it receives > an hour. Yeah, I see this on hawk too, but the question is: why? Surely for every node generating requests, there is a new node to handle those requests. Even Frost now has dramatically reduced the rate at which it requests stuff. Ian. -- Ian Clarke ian at freenetproject.org Founder & Coordinator, The Freenet Project http://freenetproject.org/ Chief Technology Officer, Uprizer Inc. http://www.uprizer.com/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 232 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20020217/04f46acf/attachment.pgp>
