httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stas Bekman <s...@stason.org>
Subject Re: mod_comment
Date Mon, 29 Nov 2004 19:11:36 GMT
Greg Stein wrote:
> On Mon, Nov 29, 2004 at 01:54:18PM -0500, Geoffrey Young wrote:
> 
>>Justin Erenkrantz wrote:
>>
>>>--On Monday, November 29, 2004 10:41 AM -0800 Greg Stein
>>><gstein@lyra.org> wrote:
>>>
>>>
>>>>but we were not allowed to remove features. Removing the fp from the
>>>>API would have disabled this "feature" in mod_perl, among others.
>>>
>>>I can't tell you how often I've been bitten personally by mod_perl
>>>trying to reparse our configuration because of this 'feature.'  It needs
>>>to go away big time. 
>>
>>sorry, but I'm not following.  can you guys be specific (code wise) about
>>what is supposed to be forbidden?  my only knowledge of mod_perl using that
>>file pointer is when implementing <Foo> containers where we (of course) need
>>to know what is between the opening and closing markers.
> 
> 
> Yup. That's the one. And to do that, you use the file pointer which
> gets passed out thru the API.

so what's the proposed replacement? If we get memmapped pointer or any 
other pointer that can be parsed instead, that will work just fine. Just 
hiding the fp from the API will make it impossible to implement custom 
containers.


-- 
__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com

Mime
View raw message