Return-Path: william@bourbon.usc.edu
Delivery-Date: Thu Apr 19 22:16:06 2007
X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on merlot.usc.edu
X-Spam-Level: 
X-Spam-Status: No, score=-3.3 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,
	NO_REAL_NAME autolearn=ham version=3.1.3
Received: from bourbon.usc.edu (bourbon.usc.edu [128.125.9.75])
	by merlot.usc.edu (8.13.5/8.13.5) with ESMTP id l3K5G6vS020203
	for <cs551@merlot.usc.edu>; Thu, 19 Apr 2007 22:16:06 -0700
Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1])
	by bourbon.usc.edu (8.13.5/8.13.5) with ESMTP id l3K5G0oj004452
	for <cs551@merlot>; Thu, 19 Apr 2007 22:16:01 -0700
Message-Id: <200704200516.l3K5G0oj004452@bourbon.usc.edu>
To: cs551@merlot.usc.edu
Subject: Re: Status Response 
Date: Thu, 19 Apr 2007 22:16:00 -0700
From: william@bourbon.usc.edu

Someone wrote:

  > The status message is meant for 2 types of functions Neighbors
  > and Files. Its fairly straightforward to differenctiate the
  > functionalities of the message type but the Respose message type
  > header is a bit ambiguous in the sense that machine
  > detecting the status respose cannot make it out as to what
  > exactly is the type of status responce its accepting( FILES of
  > NEIGHBORS)
  > 
  > We have used a low level bit to indicate the same. However the
  > specs have no mention about this . I wanted to know what
  > should be the exact method of differentiating the respose
  > messages of STATUS.

Your node can only run one user command at a time.  So,
it should know what type of status response it's waiting
for.  Right?
--
Bill Cheng // bill.cheng@usc.edu <URL:http://merlot.usc.edu/william/usc/>