Return-Path: william@bourbon.usc.edu Delivery-Date: Fri Oct 10 13:20:11 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 m9AKKBBL022384 for ; Fri, 10 Oct 2008 13:20:11 -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 m9AKR0jY031281 for ; Fri, 10 Oct 2008 13:27:00 -0700 Message-Id: <200810102027.m9AKR0jY031281@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: final proj part#1... Date: Fri, 10 Oct 2008 13:27:00 -0700 From: Bill Cheng Someone wrote: > doubts in final project part#1: > 1] Case where UOID table has been deleted after sometime interval > and after which a response for a message sent earlier has > arrived. Now it has no information to route the response to the > correct route. What step to be taken? should it be dropped or is > there any other way to handle this? You should drop the message. > 2] In case of beacon nodes- suppose A and B are two beacon nodes > and A is down for some reason. Now should B keep sending > "keepalive" messages or should it close the socket and connect > only after it gets a "hello" message after A is up? If A goes down, B should disconnect. > 3] In a case where only 1 beacon node is up and a regular node > tries to come up but inifile of the regular node has > minneighbor=2. Now what should the regular node do? Will it keep > shutting down and retry again? During JOIN, if a regular node cannot get enough join responses, it should give up, print a message to the user, and terminate itself. -- Bill Cheng // bill.cheng@usc.edu