Return-Path: 
 <cocoon-dev-return-36350-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 81108 invoked by uid 500); 6 Feb 2003 12:30:10 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 81096 invoked from network); 6 Feb 2003 12:30:09 -0000
User-Agent: Microsoft-Entourage/10.1.0.2006
Date: Thu, 06 Feb 2003 12:30:57 +0000
Subject: Re: [OT] Re: [TIPS] Basic configurations of Apache 2.0 for Cocoon
	2
From: Pier Fumagalli <pier@betaversion.org>
To: <cocoon-dev@xml.apache.org>
Message-ID: <BA680601.979E%pier@betaversion.org>
In-Reply-To: <8CB263A54D013842A2AF262CE9952ACB06D53A@feanor.pro-vision.de>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

On 6/2/03 9:42 am, "Stefan Seifert" <sseifert@pro-vision.de> wrote:

> Hello Miles.
>=20
> Thats exactly what we did for implementing a "transparent" file caching s=
ystem
> with apache 2.0 and cocoon.
>=20
> You can use something like this (with mod_rewrite enabled):
>=20
> Alias /rsvgn/ "C:/cache/rs/"
> <Directory "C:/cache/rs">
>   RewriteEngine On
>   RewriteCond %{REQUEST_FILENAME} "!-f"
>   RewriteRule (.*) http://localhost:8081/cache/engine/rs/$1 [proxy]
>   AllowOverride None
>   Options Indexes FollowSymLinks MultiViews IncludesNoExec
>   Order allow,deny
>   Allow from all
> </Directory>
>=20
> It checks if a given files exists on the local hard disk (or in one of th=
e
> subdirectory, that doesnt matter) and if this fails it redirects (invisib=
le
> for the client becaus of the [proxy] directive) the request to the servle=
t
> engine.

Talk about _HACKS_ :-) I didn=B9t know about RewriteCond... You never stop
learning

> In our case the servlet engine processes the request and - in addition to=
 that
> - writes the generated file to the hard disc, so the next time it comes f=
rom
> there without even doing a single request to the servlet engine. If the f=
ile
> gets invalidated because of a content update another process deletes the =
file
> from the file system.
>=20
> This is a special caching system which replaces the cocoon cache in some =
way
> for our special purposes. But if the cocoon cache suites you needs, you c=
an do
> the same with cocoon. But in our solution you can switch off the serlvet =
at
> all, once the cache is populated fully, and the cache is 100% transparent=
 for
> the administrator.

AAAHHHH Ugly! :-) (Hm, but it might just work in few cases)

    Pier


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org