[Catalyst] A different approach to static content

[Christopher H. Laco]

Perrin Harkins wrote:
> On Tue, 2005-08-16 at 18:10 +0100, Matt S Trout wrote:
> 
>>Returning DECLINED to apache - or just having a <Location /myapp/static>
>>block when you deploy under mod_perl - seems like a much better way to do
>>it.
> 
> 
> Agreed, those are the solutions I would recommend.
> 
> - Perrin
> 
> 

I guess that's what bugs me. Today it's /static, tomorrow it's /images, 
and next week it's /downloads and maybe it needs to be under / and not 
/myapp.

IMHO, there's no reason I should have to tweak my httpd.conf everytime 
just to serve more static from /. Especially if the someone adding 
static content is just a content creator and not the server guy. We have 
the technology. It should just work, and there's no good reason that all 
requests have to go through Catalyst when only a small percentage of 
those requese are controllers/handlers vs. static content.

But hey, maybe I'm the crazy one. Things can be made to do the right 
thing without any user intervention, so why not make live on the 
developer/installer that much easier?

-=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/0d1ddd10/smime-0001.bin