On Mon, Jun 18, 2001 at 02:58:43PM -0700, Mr. Bad wrote: > As long as you keep introducing new addresses in (preferably through > an out-of-band mechanism), and let the node run for a while, the > routing table will eventually "settle." Adding in a number of good > addresses of permanent nodes to nodes.config seems to be the best way > to do this.
It is ugly to require a flow of out-of-band addresses for a node to "settle", and IMHO it is unnecessary. It may not be fatal for a node to have dramatically more references to one node, but it is undesirable, and I suspect it could be avoided easily. > IC> By resetting your datastore on every message, getting many > IC> people pointing to your node, and then shutting it down > > This is only really a problem if a) you're not doing redundant caching > and b) the downstream nodes have -no- other addresses in them. a) Not sure what you mean b) Sure, a node could recover, but it is hardly going to be healthy for the network > Using O.O.B. mechanisms to keep adding fresh addresses is crucial > here. Only if you accept that nodes can grow dependent on one particular node, I am saying that there is no reason we can't prevent this. Relying on an O.O.B mechanism at the outset is a nescessary evil, but relying on one on an ongoing basis is definitely not a good thing. Ian. -------------- 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/20010618/10df64cb/attachment.pgp>
