On Mon, Jan 05, 2009 at 07:19:35PM +0000, Matthew Toseland wrote: > On Monday 05 January 2009 14:27, vive wrote:
> There are quite a few places on the wiki where parts of the design are > documented ... these are usually way out of date. > > > > One could of course read the code ... but it may also be hard to get the > > high-level description right-away from many details of lower-level code. :-) > > Is it possible that someone who has insight into the details of the > heuristics > > could write a short description? > > The sinking strategy is simply that we cache in the store only when an insert > is on a node which is closer to the target than any of its peers. Do you want > more details on the routing heuristics? Or to start a more general debate on > how much detailed internal documentation we should make, where we should put > it etc? I have understood how sinking works, but other major heuristics with routing and storage would be really great to see documented! I am not the guy to analyze what level of (overall) detail is best for the whole project. But these things have to go into the simulation sooner or later to make it more realistic. /v. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20090105/4c578f3f/attachment.pgp>
