On Mon, Jun 18, 2001 at 05:08:35PM -0700, [EMAIL PROTECTED] wrote:
> If a given node has X% of the datastore references, then X% of
> queries will go to it (assuming, as you say, that "a node will be
> contacted roughly in proportion to the number of references it has in
> the datastore"). If a query is successful, we will replace one of the
> existing datastore entries with the new one. There is an X% chance that
> the datastore item being thrown away points at the node in question.
>
> So there are four possibilities: either the request goes to the particular
> node (X%) or it does not (100% - X%); and either the discarded reference
> points at the particular node (X%) or it does not (100% - X%).
I think that the issue is that a request forwarded to the node
in-question, the chance that the DataSource (ie. the reference with
which a datastore entry will be replaced) will actually be *that* node
is quite high, in fact, it is 100% if that node is maliciously setting
all DataStore values to itself.
So every time a request is forwarded to my node, it increases the
probability that other requests will be forwarded to my node, and I can
artificially enhance this effect by setting all DataSources to my node
when I forward a DataReply. This is the positive feedback-loop I was
referring to.
Ian.
PGP signature
