Return-Path: william@bourbon.usc.edu Delivery-Date: Sat Oct 18 17:17:47 2008 X-Spam-Checker-Version: SpamAssassin 3.2.3 (2007-08-08) on merlot.usc.edu X-Spam-Level: X-Spam-Status: No, score=-2.3 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.2.3 Received: from bourbon.usc.edu (bourbon.usc.edu [128.125.9.75]) by merlot.usc.edu (8.14.1/8.14.1) with ESMTP id m9J0HlVF019382 for ; Sat, 18 Oct 2008 17:17:47 -0700 Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1]) by bourbon.usc.edu (8.14.2/8.14.1) with ESMTP id m9J0QZZv026624 for ; Sat, 18 Oct 2008 17:26:35 -0700 Message-Id: <200810190026.m9J0QZZv026624@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: Final Proj Date: Sat, 18 Oct 2008 17:26:35 -0700 From: Bill Cheng Someone wrote: > When a non-beacon receives the response of the join messages, it tries > to connect to all the neighbors. Well, I wouldn't put it this way. I would say, "when a non-beacon node comes up (including during a soft-restart), read its init_neighbor_list file, and try to connect to all the initial neighbors". > Now, does it have to keep trying to > connect to all the neighbors till it dies or should it just try the > connection once and if it fails, exit with an error message? It should try it only once. If it cannot connect to enough initial neighbors (i.e., less than MinNeighbors), it should delete its init_neighbor_list and do a soft-restart. -- Bill Cheng // bill.cheng@usc.edu