Return-Path: william@bourbon.usc.edu Delivery-Date: Fri Oct 17 13:34:43 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 m9HKYhgS002130 for ; Fri, 17 Oct 2008 13:34:43 -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 m9HKhEEU007752 for ; Fri, 17 Oct 2008 13:43:14 -0700 Message-Id: <200810172043.m9HKhEEU007752@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: Proj 3 Part 1 Date: Fri, 17 Oct 2008 13:43:14 -0700 From: Bill Cheng Someone wrote: > Once a non-beacon node has received a hello msg (after the joining ofcourse) > from a beacon node on atemporary connection, Does it have to use the same > socket which it used to receive the hello/join_reply for further > communication or should it try to form another connection(permanent this > time) using a different socket for doing further communication with the > beacon node. If a non-beacon node is doing a JOIN, then the connection is *not* a regular connection. Since it's not a regular connection, you must *not* exchange HELLO messages! For this JOINing non-beacon node, it should simply send a JOIN request and wait for all the responses (kind of like the client for warmup project #1). When timeout occurs (or is pressed), it should disconnect. -- Bill Cheng // bill.cheng@usc.edu