Re: [PATCH] Win32: Why explicitly futz with the file pointer?

2002-10-21 Thread William A. Rowe, Jr.
At 12:46 PM 10/20/2002, Aaron Bannert wrote: On Sun, Oct 20, 2002 at 11:30:35AM -0400, Jeff Trawick wrote: Maybe APR_APPEND needs to be cheap/simple append a la stdio append: we seek to the end of the file at open time and forget about it after that. Then we need new APR_WRITE_AT_END or

Re: [PATCH] Win32: Why explicitly futz with the file pointer?

2002-10-20 Thread Aaron Bannert
On Sun, Oct 20, 2002 at 11:30:35AM -0400, Jeff Trawick wrote: Maybe APR_APPEND needs to be cheap/simple append a la stdio append: we seek to the end of the file at open time and forget about it after that. Then we need new APR_WRITE_AT_END or something better named which is the expensive

Re: [PATCH] Win32: Why explicitly futz with the file pointer?

2002-10-20 Thread Jeff Trawick
Aaron Bannert [EMAIL PROTECTED] writes: On Sun, Oct 20, 2002 at 11:30:35AM -0400, Jeff Trawick wrote: Maybe APR_APPEND needs to be cheap/simple append a la stdio append: we seek to the end of the file at open time and forget about it after that. Then we need new APR_WRITE_AT_END or

Re: [PATCH] Win32: Why explicitly futz with the file pointer?

2002-10-20 Thread rbb
On Sun, 20 Oct 2002, Bill Stoddard wrote: Why do we need to call SetFilePointer to each call of apr_file_write()? In the common case where only threads in a single process write to a file, calling SetFilePointer is a waste of cycles. If threads from multiple processes are writing to a file,