Return-Path: william@bourbon.usc.edu Delivery-Date: Wed Nov 19 19:51:49 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.4 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 mAK3pnYv004329 for ; Wed, 19 Nov 2008 19:51:49 -0800 Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1]) by bourbon.usc.edu (8.14.2/8.14.1) with ESMTP id mAK3mxmA014030 for ; Wed, 19 Nov 2008 19:48:59 -0800 Message-Id: <200811200348.mAK3mxmA014030@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: Project Part 2: Get command Date: Wed, 19 Nov 2008 19:48:59 -0800 From: Bill Cheng Someone wrote: > When we do a "get ", and successfully retrieve a file, > Suppose another file with the same filename exists in the Nodes Current > Working Directory. In this case, the User is asked if he/she "wants to > overwrite the file", right?(Also at this stage there is a file created in > the files directory for e.g. 3.data) Yes. > Now, suppose the user says He DOESNOT want to overwrite the file.So, should > the 3.data in the files directory be deleted and should this node not serve > the file anymore? 3.data should *not* be deleted. This situation is analygous to the case where the user decides to keep the file in the current working directory and later delete the copy in the current working directory. In a way, what happens in the current working directory should not affect what goes on on the server side of the node. -- Bill Cheng // bill.cheng@usc.edu