On Tuesday 23 September 2003 12:22 am, Todd Walton wrote: > > If there are other nodes on the network that you trust, you could > > exchange this information with them, and have a much better idea of their > > specialization. Also this could also provide a basis for a > > non-alchemistic gage for what data should put in the store and what > > should be removed. > > You switched horses. Some Guy was talking about routing times, and you're > talking about specialization. If you're talking about swapping > specialization info with other nodes, then why not just look in the local > datastore at what keys there are? You wouldn't need to do what Some Guy > was talking about.
Fair enough. While all of the above could be done without collecting that data, it would be better if it was available. I say this because it requires a much lower level of trust to give someone your "10 points" routing estimate than to trust them with the exact keys of all the data in your store. Also if NGrouting provides the mechanism for where the data requests come from, doesn't it make seance to use those same mechanism to determine where it is stored? Yes, strictly speaking it is not necessary, as you can already compute relative specialization and popularity of data, however ultimately you are trying to approximate what you will be seeing requests for in the future, and the time estimates provide that. I would agree however that this would not be better if it meant using a lot of CPU time or a huge amount of memory, however I don't think that would be the case. _______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
