On Tue, Jul 03, 2001 at 09:13:14AM -0700, Ian Clarke wrote:
<>
> > Add to that the dubious topological effects of such a presence and you
> > have yourself a big headache.
>
> This is a separate issue, the announcement protocol is designed to
> counter such an effect. The current network topology survived the much
> more blunt instrument of inform.php.
I don't think this is true:
- If the central element does accept references from the new nodes, then
there is a risk that we end up with a topological problem not unlike the
current one (and as Tavin pointed out, the current network has _not_
survived), where the nodes an announcee is introduced only to are those
nodes which were announced only a short while ago (because the central
node is loosing all other references fast). If the central node does not
accept references from announcees, then we can once and for all reject
the "this is just a default" argument, and also I'm not sure it makes
things better - if the central node accepts the references then they are
at least gaining one fairly trusted peer...
- The network learns about the announcee through the announcement
protocol, which I agree does spread things out to some extent, but the
announcee learns about the network by making normal data requests (which
makes another point, the bandwidth load on the central node would be
VERY large, since initial requests go through it - do you want your
companies pipe saturated by that? Security is not the only reason we
decentralize...), which do not spread the references very well.
--
'DeCSS would be fine. Where is it?'
'Here,' Montag touched his head.
'Ah,' Granger smiled and nodded.
Oskar Sandberg
[EMAIL PROTECTED]
_______________________________________________
Devl mailing list
[EMAIL PROTECTED]
http://lists.freenetproject.org/mailman/listinfo/devl
