Return-Path: william@bourbon.usc.edu Delivery-Date: Thu Oct 9 19:13:04 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 m9A2D4M1010978 for ; Thu, 9 Oct 2008 19:13:04 -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 m9A2JfSj016671 for ; Thu, 9 Oct 2008 19:19:41 -0700 Message-Id: <200810100219.m9A2JfSj016671@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: join question Date: Thu, 09 Oct 2008 19:19:41 -0700 From: Bill Cheng Someone wrote: > When a non-beacon node, with no init neighbor file, makes a temporary > connection to a beacon node for the join process, should it send a NOTIFY to > the beacon node after join timeout expires. There is no need. NOTIFY is like GOOD-BYE. You don't need to say GOOD-BYE if you didn't say HELLO in the first place. > Otherwise how will the beacon node know that the connection is closed. Just like warmup #1, if you shutdown() the socket and then close() it, the other side should detect pretty soon. -- Bill Cheng // bill.cheng@usc.edu