>>>>> "NB" == Neil Barsema <neil at barsema.org> writes:
NB> I still think limiting the number of references to a specific
NB> node is a nescesary feature.
OK, let's say that we limit the number. Are we going to limit it to an
absolute # (1000), or to a percentage of what's in the data store? If
we do it by percentage, is it a percentage of all the items in the
store, or a percentage of the references in the store?
I have 3 transient nodes behind a firewall. They all have a single
address to use in nodes.config -- the firewall machine's node. Do THEY
now have to have 9 other addresses (which BTW they can't connect to)?
If a node has TWO good peers, equally distributed, which one do we
reduce?
If a node only has the address of ONE GOOD PEER, how will we achieve
limiting that address to N% of the referenced data store items?
How does the reduction happen? As a periodic clean-up step, with
wholesale slaughter of references? Skipping over references during
routing (so that requests get sent to under-represented nodes)? What
if path-folding on a response from an under-represented node would add
a reference to the over-represented node?
~Mr. Bad
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Mr. Bad <mr.bad at pigdog.org> | Pigdog Journal | http://pigdog.org/
"Your description of coffee is how you interpret Sex."
-- "Personality Quiz" chain letter
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
_______________________________________________
Devl mailing list
Devl at freenetproject.org
http://lists.freenetproject.org/mailman/listinfo/devl
