Return-Path: william@bourbon.usc.edu Delivery-Date: Fri Sep 5 21:33: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.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 m864XnH8014053 for ; Fri, 5 Sep 2008 21:33:49 -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 m864WDNG009832 for ; Fri, 5 Sep 2008 21:32:13 -0700 Message-Id: <200809060432.m864WDNG009832@bourbon.usc.edu> To: cs551@merlot.usc.edu Subject: Re: Sending of file in get Date: Fri, 05 Sep 2008 21:32:13 -0700 From: Bill Cheng Someone wrote: > For GET, I am sending the file 1 byte at a time as usual. I am reading > the file character by character and simultaneously sending it and > receiving and creating MD5 simultaneously. > In other words, I am not using the 512 byte buffer for transfer. > Is this fine ? Sure! On the server side, are you reading the file from disk one byte at a time (which would be just fine)? You can read 512 bytes at a time from the disk and write to the socket one byte at a time. -- Bill Cheng // bill.cheng@usc.edu