On 4 Jan 2003, Joe Schaefer wrote: > To answer my own question :-), this line in apr_buckets.h describes the > "read" method for buckets: > apr_status_t (*read)(apr_bucket *b, const char **str, apr_size_t *len, > I interpret the const qualifier here to mean that modifications (to > the raw data) are disallowed by the bucket API, and that the setaside > implementation for heap-type buckets is fine as-is. Is this correct?
That's correct. In all except one sooper-sekret ;) case, buckets are write-once. And even in the sooper-sekret case (which is apr_brigade_write), it's not modifying the existing contents of the bucket... only appending to the bucket. --Cliff
