apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cliff Woolley <cliffwool...@yahoo.com>
Subject Re: bucket and brigade sizes
Date Thu, 24 Jan 2002 17:40:14 GMT
On Thu, 24 Jan 2002, Greg Stein wrote:

> This isn't a hard problem, people...
> * a bucket can be a FILE, which means it could represent >2G of data. thus,
>   its size is apr_off_t.
> * if a single bucket is an apr_off_t, then a whole brigade will be, too
> * read() is reading into memory, so it must be apr_size_t
> * flatten() reads into memory, so it must be apr_size_t
> * partition() doesn't have to read into mem, so its point is apr_off_t
> So now somebody is going to say, "but how can read() be less than the
> bucket?" Hello... we do it all the time. You read a *portion* and convert
> the bucket to something else. You then insert a new bucket after 'self' for
> the unread portion.

I'm sold.  ++1

   Cliff Woolley
   Charlottesville, VA

View raw message