Return-Path: william@bourbon.usc.edu
Delivery-Date: Sun Apr 15 08:53:18 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 l3FFrInj019380
	for <cs551@merlot.usc.edu>; Sun, 15 Apr 2007 08:53:18 -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 l3FFrSrh005662
	for <cs551@merlot>; Sun, 15 Apr 2007 08:53:28 -0700
Message-Id: <200704151553.l3FFrSrh005662@bourbon.usc.edu>
To: cs551@merlot.usc.edu
Subject: Re: FileID 
Date: Sun, 15 Apr 2007 08:53:28 -0700
From: william@bourbon.usc.edu

Someone wrote:

  > Other than creating a search reply message,
  > at what other occasion will a node create
  > File ID for a file?

None, if the above is your approach.

You can also take another approach.  When you save a file
into cache or permanent space, you create the FileID.  But
now you have to save the FileID in the mini-filesystem.
With the first approach, you can only keep the FileIDs in
memory.
--
Bill Cheng // bill.cheng@usc.edu <URL:http://merlot.usc.edu/william/usc/>