httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tony Finch <>
Subject Re: [PATCH] Filter registration.
Date Fri, 28 Jul 2000 22:19:59 GMT
"Roy T. Fielding" <fielding@kiwi.ICS.UCI.EDU> wrote:
>>But then the data has changed too, so you still have the situation
>>that the lifetime of the bucket is the same as its contents. The same
>>is true for the bottom filter if it concatenates the buckets when it
>>saves the contents: the old data and buckets are destroyed and
>>replaced by new ones. I think that if you keep the bucket and content
>>lifetimes the same then it will simplify the rules you have to follow
>>to ensure that buckets are used correctly.
>The data doesn't change -- it gets copied to other places, or new
>references to it are created.

Yes, that's what I meant. The new bucket refers to different data from
the old bucket.

>E.g., when we truncate a bucket, all we are doing is reducing the
>length size within the bucket structure.

Yes, this is why things like HEAP buckets and MMAP buckets have to
have a reference counting mechanism so that the underlying resource is
freed when all of its buckets disappear. However, when you don't want
to leave resource management to the bucket code you use IMMORTAL
buckets which mean "lay off, this is my data".

>I'm not sure how far we can go with that, since some data sources can
>only be "read" from a single point.

Are you referring to PIPEs here? I described a way of dealing with
them inside this design.

297 the humor dial's lowest setting

View raw message