apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe, Jr." <wr...@rowe-clan.net>
Subject RE: cvs commit: apr-util STATUS
Date Sat, 09 Dec 2000 19:02:54 GMT
> From: Cliff Woolley [mailto:cliffwoolley@yahoo.com]
> Sent: Saturday, December 09, 2000 12:52 PM
> 
> > On the other hand, brigade_split_offset does seem useful to me.  Consider a filter
> > that does some sort of compression or encoding that requires the data to be split
> > into blocks of a predetermined length, regardless of what's actually in those
> > blocks.
> 
> Okay, so that wasn't the best example, since a compression or encoding filter would
> have to read the data to compress or encode it anyway.  Bah.  What I was really
> trying to get at was something more like the byterange filter.  Why is it that an
> ap_brigade_split_offset would not work there again?

How about a better example, a binary result filter from a known filetype.  E.g. we
have this .gif image that we know from the header we will play with a certain range
of bytes in the body, so ap_brigate_split_offset forward to that part.  Certain
.pdf manipulators could use this as well.

This is now apr-util, so it should be something generally useful outside of the
server for other bucket brigade apps.


Mime
View raw message