Date: 2005-01-16T02:18:48 Editor: MarkLundquist Wiki: Cocoon Wiki Page: ServingStaticFiles URL: http://wiki.apache.org/cocoon/ServingStaticFiles
no comment Change Log: ------------------------------------------------------------------------------ @@ -24,7 +24,7 @@ }}} ---- -''IMHO this is overengineered, because in order to serve static content directly from Apache (see below) the URI-to-filesystem mapping in the example above must also be implemented in the Apache configuration. Cocoon already needs a separate rule for each (in order to specify the MIME type), but Apache doesn't, so it's a pain to have to add it just so that URIs don't have to start with "images/", etc.'' --[wiki:MarkLundquist ML] +''IMHO this is overengineered, because in order to serve static content directly from Apache (see below) the URI-to-filesystem mapping in the example above must also be implemented in the Apache configuration. Cocoon already needs a separate rule for each (in order to specify the MIME type), but Apache doesn't, so it's a pain to have to add it just so that URIs don't have to start with "images/", etc. See the simpler version of these sitemap rules given in SimpleModProxy under "Serving Static Content".'' --[wiki:MarkLundquist ML] ---- It's more efficient to serve static files from Apache (see SimpleModProxy), but we still want our Cocoon app to have the ability to serve static content all by itself without Apache, for when we're developing in a non-server (desktop/laptop) environment.
