On Tue, Jun 26, 2001 at 12:34:14PM +0200, Neil Barsema wrote: > Tavin wrote: > > Now, in the 0.4 routing table we have a hard limit on the number of > > refs and the number of nodes. Currently we're using default values > > of 1000 and 100 respectively. So when the maxNodes limit is exceeded, > > I am dropping the node with the lowest ref count. > > > > My proposal? I'd like to drop the node with the _highest_ ref count > > instead. > > I think this is an interesting Idea, however I also think it is a bit too > drastic. I am afraid to much information will be lost. > > But Taking your idea and pushing and prodding it I arrived at this aproach: > > If the maxNodes limit is exceeded the node for wich the newest reference is > the oldest is deleted. So the node for wich we have the least reliable > information. regardles of size. > and if the maxreference limit is reached, the oldest reference of the > biggest node is removed. > This would also cause the nodes to be equal in size over time.
I think it's computationally infeasible, unless we want to make the routing table suck up ridiculous amounts of memory and processor time. -- # tavin cole # # "Technology is a way of organizing the universe so that # man doesn't have to experience it." # # - Max Frisch _______________________________________________ Devl mailing list Devl at freenetproject.org http://lists.freenetproject.org/mailman/listinfo/devl
