Brandon writes:
I agree that it should go in the contrib directory until it`s
sufficiently mature, integrated, useful, and modular to be
part of the main tree, especially since we`re about to release
another version. We certainly don`t want any new, untested code
in the new release.
OK, done (and thanks for the words of encouragement). I'll stuff
patches into contrib/ RSN.
Howeve, at this point, I reiterate my plea/offer for some sort of
pluggable system for mechanisms to deal with messages. Without
something like that, I simply don't see a modular way to incorporate
this sort of code -- it has to be intimately wound into the Request
code as things currently stand, as it needs to come after a search for
the data in the local store but before the TCP transmission to the next
likely node. Negative caching (where a key isn't looked up if a recent
lookup at the same depth already failed) would have the same problem
(presuming it's useful, which I doubt).
_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
