Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Mime-Version: 1.0 (Apple Message framework v752.2)
In-Reply-To: <813716b60710201359l2b52b339q3457d7589aec26f2@mail.gmail.com>
References: <813716b60710201359l2b52b339q3457d7589aec26f2@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <1D9F61DA-812B-43B5-8CBB-8B49209CF0EA@jaguNET.com>
Content-Transfer-Encoding: 7bit
From: Jim Jagielski <jim@jaguNET.com>
Subject: Re: mod_substitute docs
Date: Mon, 22 Oct 2007 09:29:15 -0400
To: dev@httpd.apache.org


On Oct 20, 2007, at 4:59 PM, Vincent Bray wrote:

> Hullo,
>
> I'm attempting to document this module but can't figure out what the f
> (flatten) flag does (bucket brigade munging makes my eyes cross). Any
> clues?
>

Say you are looking for 'foo' and have a bucket that
contains 'jimfoojag'. The fast way to handle this would
be to split off 3 buckets from this, one containing
'jim', the other containing 'jag' and the middle one that
contains the substitute for 'foo' (say it's 'bar'). The rub
is that the pattern matching looks at buckets only, so you
wouldn't see a full bucket that contains 'jimbarjag' and
so if you had a search for 'mbarj', it would be missed using
the "fast way". In the slow way (flattening), instead
of creating the 3 buckets, you go ahead and smash them all
together resulting in the single bucket that now contains
'jimbarjag'. Now the search for 'mbarj' would succeed.

> Here's a start anyway:
>
> http://people.apache.org/~noodl/mod_substitute.xml
>
> -- 
> noodl
>