[Catalyst] A different approach to static content

[Christopher H. Laco]

Wade.Stuart at fallon.com wrote:
> 
> 
> 
> I guess I may be missing the point but why not serve the static files
> outside of the mod_perl/catalyst owned url space and be done with it.
> 
> -Wade

You can. Sometimes that's not possible, or desireable. If the Catalyst 
app has to live at /, you may still want static content littered around 
/, like /images, /css, /downloads, /flash, etc. Maybe the Catalyst app 
is being hoisted into an existing site with static content everywhere in /.

There's many different situations, and many different ways to tackle 
static content. They're all right depending on the situation. I'm simply 
looking at another option; with [theoretically] less or no configuration 
changes needed on the web server to coexist with static content.

-=Chris

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3178 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.rawmode.org/pipermail/catalyst/attachments/20050816/a777a609/smime-0001.bin