Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 79293 invoked from network); 7 Jan 2004 19:53:07 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 7 Jan 2004 19:53:07 -0000 Received: (qmail 77254 invoked by uid 500); 7 Jan 2004 19:52:52 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 77221 invoked by uid 500); 7 Jan 2004 19:52:52 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 77207 invoked from network); 7 Jan 2004 19:52:52 -0000 Received: from unknown (HELO ares.cs.Virginia.EDU) (128.143.137.19) by daedalus.apache.org with SMTP; 7 Jan 2004 19:52:52 -0000 Received: from cobra.cs.Virginia.EDU (cobra.cs.Virginia.EDU [128.143.137.16]) by ares.cs.Virginia.EDU (8.12.10/8.12.10/UVACS-2003031900) with ESMTP id i07JqslZ015012 for ; Wed, 7 Jan 2004 14:52:55 -0500 (EST) Date: Wed, 7 Jan 2004 14:52:54 -0500 (EST) From: Cliff Woolley X-X-Sender: jcw5q@cobra.cs.Virginia.EDU To: dev@httpd.apache.org Subject: Re: Save brigade and buckets In-Reply-To: <3FFC03C8.6080501@web.turner.com> Message-ID: References: <3FFC03C8.6080501@web.turner.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Wed, 7 Jan 2004, Brian Akins wrote: > This may not be apache-dev related, but I do not know where else to ask it. > Is it possible to save an entire bucket bridade (including it's buckets) > across requests. I looked at ap_save_brigade, but I'm sure that will > work. It seems that the brigades are always tied to a connection. Brigades are tied to the pool in which they are created. Buckets for the most part have no inherent lifespan, other than the fact that if you leave them in a brigade and destroy the brigade, the buckets in it will be deleted. (The exception is that you should "setaside" each bucket into the new pool to make sure any underlying data lives as long as the bucket itself does.) Exactly what kind of lifespan are you wanting for your brigade? It should just be a matter of getting a pool with that lifespan, making a brigade in it, and calling setaside on the buckets and then moving them over to that new brigade. That's basically what ap_save_brigade() does. --Cliff