Return-Path: william@bourbon.usc.edu Delivery-Date: Mon Nov 24 20:08:16 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 mAP48G19006471 for ; Mon, 24 Nov 2008 20:08:16 -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 mAP46mun032301 for ; Mon, 24 Nov 2008 20:06:48 -0800 Message-Id: <200811250406.mAP46mun032301@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: CS551: Final Project: Get and Search Timeout Date: Mon, 24 Nov 2008 20:06:48 -0800 From: Bill Cheng Someone wrote: > What would be the time out values for Get and Search responses ? > > For search is it valid to assume it as MsgLifeTime ? Same as other message types. > And for get, can we assumet it as GetMsgLifeTime ? Of course! > Also, what would be the behaviour when we press ctrl c when a get command is > in progress ?? means short-circuit (as explained before). So, if you have not received all the data for the file you are receiving, you should delete what you have received so far. -- Bill Cheng // bill.cheng@usc.edu