On Mon, 08 May 2000, Brandon wrote:
> I've covered this a few times. All we need is to add filtering to
> Request. Add a field to Request that contains a list of CHKs. The node
> will ignore any key matches if matched file has the same CHK was one in
> the list. That way it will be _exactly_ like sending a normal request,
> smart routing and all, but it simply won't see the files that it isn't
> supposed to see.
And I have rejected it several times.
If you allow different pieces of data to be routed by the same key, then you
get related data routed to the same nodes. Which is exactly what we are trying
to get away from.
And it will only get worse because if KHKs are not unique, then they move from
being specific names to keywords, and you will end up with hundreds of
documents under ever KHK containing related data, and all routed so that it is
prone to targeted attack. Not good.
--
Oskar Sandberg
md98-osa at nada.kth.se
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
_______________________________________________
Freenet-dev mailing list
Freenet-dev at lists.sourceforge.net
http://lists.sourceforge.net/mailman/listinfo/freenet-dev
