Return-Path: william@bourbon.usc.edu Delivery-Date: Sun Oct 26 18:34:23 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 m9R1YNV5012132 for ; Sun, 26 Oct 2008 18:34:23 -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 m9R1j87X024939 for ; Sun, 26 Oct 2008 18:45:08 -0700 Message-Id: <200810270145.m9R1j87X024939@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: When non-beacon starts Date: Sun, 26 Oct 2008 18:45:08 -0700 From: Bill Cheng Someone wrote: > When a first non-beacon node comes up, Is it assumed that all beacon > nodes are up and are fully connected ? No. This is a peer-to-peer network where every node can be controlled independently by its owner. You really cannot assume anything. It's possible that none of the beacon nodes are up. Your node needs to behave properly under any condition! -- Bill Cheng // bill.cheng@usc.edu