I have merged Robert's original patch (compile fixed) for depth-first announcement onto a branch, opennet-changes.
It will need to be tested thoroughly: - Do new nodes announce with new seeds? - Do new nodes announce with old seeds? - Do old nodes announce with new seeds? (Note that Update Over Mandatory relies on announcement, as well as announcing existing nodes) However, it is a very small patch, and since we wait for transfers to complete *after* we call addRefIfWanted(), it should be okay. IMHO the theoretical justification for this patch is more than adequate: - The nodes at the "end" of the announcement path should reply first. They are much less likely to be overloaded. - They are also closer to the target location, so announcement should be more effective. However, I suspect the difference in practice will be nil: - We will receive the same set of announcement offers, just backwards. - We will accept all of them because we are a newbie, and normally we get rather fewer announcement offers than our connection limit. => Getting more seednodes (preferably via an automated process) is more important. Thoughts?
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Devl mailing list Devl@freenetproject.org https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
