Return-Path: william@bourbon.usc.edu
Delivery-Date: Tue Nov 25 22:09:09 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.4 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 mAQ698dW020224
	for <cs551@merlot.usc.edu>; Tue, 25 Nov 2008 22:09:09 -0800
Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1])
	by bourbon.usc.edu (8.14.2/8.14.1) with ESMTP id mAQ67v8c017749
	for <cs551@merlot>; Tue, 25 Nov 2008 22:07:57 -0800
Message-Id: <200811260607.mAQ67v8c017749@bourbon.usc.edu>
To: cs551@merlot.usc.edu
Subject: Re: Join and Check
Date: Tue, 25 Nov 2008 22:07:57 -0800
From: Bill Cheng <william@bourbon.usc.edu>

Someone wrote:

  > Since join and check are not there, what does a non beacon do after 
  > receiving a notify?

Log it!

  > Should it just continue to participate in the connection.

Yes.

  > So, if its neighbor count falls below min neighbors, it should just exit ?

It should not work like that even for part (1)!  Remember,
MinNeighbor is only checked when a node *comes up*.
--
Bill Cheng // bill.cheng@usc.edu <URL:http://merlot.usc.edu/william/usc/>