You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Pier Fumagalli <pi...@betaversion.org> on 2003/02/06 13:15:30 UTC
Re: [OT] Re: [TIPS] Basic configurations of Apache 2.0 for Cocoon
2
On 6/2/03 1:39 am, "Miles Elam" <mi...@pcextremist.com> wrote:
> Here's a question for all you HTTPd heads out there. ;-)
>
> Is it possible now or reasonably straightforward to have HTTPd look for
> a static file and, upon failure, look up a fallback resource? For
> example, if a user requests "/images/foo.png", HTTPd would look up the
> file on the filesystem. If the file wasn't there, it would pass it to
> the servlet engine (or whatever dynamic process available). Hell, even
> better: "/images/foo" that invokes HTTPd's content negotiation and then
> checks the dynamic pool(s).
>
> It's got filters now to pass the output of one module to the input of
> another, but what about a process similar to nested try/catch blocks?
> The first, most efficient method fails, fall back to the next, and the
> next...
Nope... (It would be just plain wrong IMO).
Pier
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
Re: [OT] Re: [TIPS] Basic configurations of Apache 2.0 for Cocoon
2
Posted by Pier Fumagalli <pi...@betaversion.org>.
On 6/2/03 12:15 pm, "Pier Fumagalli" <pi...@betaversion.org> wrote:
> On 6/2/03 1:39 am, "Miles Elam" <mi...@pcextremist.com> wrote:
>
>> Here's a question for all you HTTPd heads out there. ;-)
>>
>> Is it possible now or reasonably straightforward to have HTTPd look for
>> a static file and, upon failure, look up a fallback resource? For
>> example, if a user requests "/images/foo.png", HTTPd would look up the
>> file on the filesystem. If the file wasn't there, it would pass it to
>> the servlet engine (or whatever dynamic process available). Hell, even
>> better: "/images/foo" that invokes HTTPd's content negotiation and then
>> checks the dynamic pool(s).
>>
>> It's got filters now to pass the output of one module to the input of
>> another, but what about a process similar to nested try/catch blocks?
>> The first, most efficient method fails, fall back to the next, and the
>> next...
>
> Nope... (It would be just plain wrong IMO).
I stand corrected by Stefan... You _never_ stop learning.
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org