On Tue, 7 Aug 2001, Roy T. Fielding wrote: > It only imposes the restriction that a routine cannot morph a bucket > without also morphing the contents of that bucket, which in some cases > means transferring the data and freeing the old allocation.
You have to use the original apr_bucket struct for the new morphed bucket because you mess up the brigade otherwise, and even if you tried to account for that, you'd still probably invalidate bucket pointers in the caller. > I would think that the bucket memory allocator and the bucket memory > deallocator would have to be consistent. Put it in the pool. Huh? What pool? --Cliff -------------------------------------------------------------- Cliff Woolley [EMAIL PROTECTED] Charlottesville, VA
