Delivery-Date: Sun Oct 26 13:27:43 2008
Message-Id: <200810262038.m9QKcPnK021370@bourbon.usc.edu>
To: cs551@merlot.usc.edu
Subject: Re: csci-551 final#1
Date: Sun, 26 Oct 2008 13:38:25 -0700
From: Bill Cheng <william@bourbon.usc.edu>

Someone wrote:

  > How is the check request msg going to get initiated..? I suppose it is to be
  > handled via commandline but i couldn't find its format in the spec.

Not via commandline.  In paragraph 6 of the Peer-to-Peer
section of the spec:

    http://merlot.usc.edu/cs551-f08/projects/final.html#p2p

it says:

    When a node loses connection with one of its neighbors,
    it is possible that it may be disconnect from the SERVANT
    network. In order to make sure that it is still connected
    to the network, the node must intiatiate a connectivity
    check by flooding a check message.

So, you must flood a CHECK when you lose *any* connection
with a neighbor (unless this node is shutting down of course).

  > Also it is mentioned in the spec that 'The flooding of check messages stops
  > at a beacon node where the beacon node sends a check response message
  > towards the node from which it received the check message'. What should the
  > requesting node of check msg set the TTL to to ensure that it stops at a
  > beacon node and not anywhere before.

You should use the TTL from the startup configuration file.

  > The timeout we can use for check response msg is JoinTimeOut, right ?

No.  You should use the same logic as for the status command:

    http://merlot.usc.edu/cs551-f08/projects/final-faq.html#done-status
--
Bill Cheng // bill.cheng@usc.edu <URL:http://merlot.usc.edu/william/usc/>