Return-Path: william@bourbon.usc.edu Delivery-Date: Fri Oct 17 06:22:00 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 m9HDM0Cw029809 for ; Fri, 17 Oct 2008 06:22:00 -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 m9HDURZA014332 for ; Fri, 17 Oct 2008 06:30:27 -0700 Message-Id: <200810171330.m9HDURZA014332@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: Proj 3 Part 1 Date: Fri, 17 Oct 2008 06:30:27 -0700 From: Bill Cheng Someone wrote: > I have the following doubt: > After the beacon network is set up, a non-beacon comes to join the > network. It exchanges the join message and gets the response from all > the nodes through the beacon it contacted in the beginning. > Now, it connects to everyone that satisfy the distance constraint. I > want to know the amount of time the beacon should wait before closing > the connection if it did not receive a connection request from the non > beacon. I guess this applied to any connection, not just the one you described above. So, the question is, if you connect to another node and the other node never sends you anything, when should you timeout? I think you can just use the KeepAliveTimeout for this situation. -- Bill Cheng // bill.cheng@usc.edu