Return-Path: william@bourbon.usc.edu Delivery-Date: Wed Sep 10 20:22:41 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.3 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 m8B3Mfxl029209 for ; Wed, 10 Sep 2008 20:22:41 -0700 Received: from bourbon.usc.edu (localhost.localdomain [127.0.0.1]) by bourbon.usc.edu (8.14.2/8.14.1) with ESMTP id m8B3MHI3026572 for ; Wed, 10 Sep 2008 20:22:17 -0700 Message-Id: <200809110322.m8B3MHI3026572@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: Slow Client Date: Wed, 10 Sep 2008 20:22:17 -0700 From: Bill Cheng Someone wrote: > For the test case > > ./server -m 12345 > (then immediately run the following in one or multiple > windows, this should start a long transfer) > ./client get -m localhost:15096 /home/scf-22/csci551b/public/cali.wav > (press c in the server window and see what happens) > (if transfers ends, it's good) > (if transfers does not end within 2 seconds, > take at least 2 points, off; the longer the wait, > the more points to take off) > > In my case the client is running very slowly . So the server and > client are asynchronously. For instance if server sends 100 bytes > then client is receiving 50 bytes and so on. So at the time when > server gets interruptĀ  and closes the client is still receivingĀ  > the data. The client ends only after it gets all the bytes send > by server. > > As discussed after class told , you said it might be because the > client is still receiving data from buffer or MD5 calculation is > taking time. > However is this behaviour acceptable? I cannot answer question of this type in e-mail. Please see the 3rd bullet at: http://merlot.usc.edu/cs551-f08/description.html#email -- Bill Cheng // bill.cheng@usc.edu