Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 15641 invoked by uid 500); 2 Apr 2002 04:38:55 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 15630 invoked from network); 2 Apr 2002 04:38:54 -0000 Date: Mon, 1 Apr 2002 23:34:03 -0500 (EST) From: Cliff Woolley X-X-Sender: root@deepthought.cs.virginia.edu To: "William A. Rowe, Jr." cc: Bill Stoddard , Subject: Re: apr_bucket_file_create() args... In-Reply-To: <5.1.0.14.2.20020401222055.02120838@localhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Mon, 1 Apr 2002, William A. Rowe, Jr. wrote: > At 10:14 PM 4/1/2002, FirstBill wrote: > > >Humm... I would be suprised if sendfile has a limit like this. If it > >does, then it is a bug in the OS IMHO. In principle, sendfile should > >work on any file supported by the OS... > > Where do you see 64 bits of size here? > BOOL TransmitFile( > ... > ); As an aside, I find the 56MB number totally unsurprising. I've seen WriteFile() on win2k do the same thing (also at right around 56MB). We were getting these baffling file corruptions and couldn't figure out what was going on... until we figured out it was just one the damn writes failing, saying there were insufficient resources to complete the operation. (I forget the exact error code.) We had to write a utility function to loop on WriteFile() with bite-sized chunks, and then it worked. Ridiculous. --Cliff -------------------------------------------------------------- Cliff Woolley cliffwoolley@yahoo.com Charlottesville, VA