Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Message-ID: 
 <871AECEC74582541923203963967BBFF01B7BD6B@cnfqe058.cnf.prod.cnf.com>
From: "Bennett, Tony - CNF" <Bennett.Tony@cnf.com>
To: "'dev@httpd.apache.org'" <dev@httpd.apache.org>
Subject: RE: mod_dav overhaul
Date: Wed, 28 May 2003 15:36:57 -0700
MIME-Version: 1.0
Content-Type: text/plain

If this is a wish list...
I'd kinda like to see dav_fs_set_headers() (in repos.c)
be able to handle content-type.
Here's the comment contained in that function:
    /* ### how to set the content type? */
    /* ### until this is resolved, the Content-Type header is busted */

-tony

-----Original Message-----
From: William A. Rowe, Jr. [mailto:wrowe@rowe-clan.net] 
Sent: Wednesday, May 28, 2003 2:00 PM
To: dev@httpd.apache.org
Subject: Re: mod_dav overhaul


At 02:50 PM 5/28/2003, Cliff Woolley wrote:
>On Wed, 28 May 2003, William A. Rowe, Jr. wrote:
>
>> It makes me wonder... today we have to create and destroy the pool. 
>> But what about reuse?  The overhead of creating the pool itself?  It 
>> seems like a good extention to the apr_pool api if we had an 
>> apr_pool_recycle function that would do the usual pool cleanups and 
>> frees, but let us reuse the pool's own memory without getting tangled 
>> in thread locking.  For any symmetrical use of pools (where each 
>> recycle is generally similar in footprint to the prior allocations) 
>> this could be pretty sweet.
>
>You can do what you suggest by just doing an apr_pool_clear() and then 
>reuse the pool, no?  There's the max_mem_free thing, but other than 
>that...

Ok, I was caught unaware :-)  Time to refactor some bits of mod_autoindex
:-)