Return-Path: william@bourbon.usc.edu Delivery-Date: Mon Oct 13 07:36:46 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 m9DEajDg003204 for ; Mon, 13 Oct 2008 07:36:45 -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 m9DEiEO6031275 for ; Mon, 13 Oct 2008 07:44:14 -0700 Message-Id: <200810131444.m9DEiEO6031275@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: 551- final Date: Mon, 13 Oct 2008 07:44:14 -0700 From: Bill Cheng Someone wrote: > - For a beacon node, it needs to connect to all other beacon ndoes. > > Since a beacon does not send any message on a connect to another beacon, how > does the beacon know that it has received a connection from a beacon node? > > or am I missing something? I read the previous posts, but couldn't figure > this out. On a "regular" connection, two nodes (it doesn't matter if they are beacon nodes or non-beacon nodes) *must* exchange HELLO as the first message. -- Bill Cheng // bill.cheng@usc.edu