On Thu, 30 May 2002, Ryan Bloom wrote: > > True, but I thought part of the idea behind buckets is so that the > > backing type doesn't have to be known. > > Exactly!
Exactly. All you really need to test here is length. If the bucket is zero bytes, that's all you need to know. That gets you all metadata buckets handled in one fell swoop. If there are certain kinds of metadata buckets a filter *does* know about and want to handle specially (eg EOS or FLUSH), it can make the choice to special case those. > Every bucket can be read. That is a mandatory function that all buckets > must implement. If the back-end bucket-type isn't know, the filter can > ALWAYS do a read/apr_bucket_make_heap. True. Though we've specified the additional semantics that apr_bucket_read() causes the bucket to auto-morph into one that is in-memory. Either way. --Cliff
