[Catalyst] Plugin::Static::Real RFC and Qs

apv apv at sedition.com
Sat Jan 28 20:26:02 CET 2006


Awhile back I shared a snippet for writing the view output to disk in 
conjunction with an .htaccess setup that would serve real files if they 
existed, or else give the URI to Catalyst. For sites that have rarely 
changing sections it would give a huge performance increase (unless 
you've got more memory for caching than you know what to do with).

http://lists.rawmode.org/pipermail/catalyst/2005-November/002429.html

I am thinking of redoing it (haven't looked at it since) as a plugin 
and I'm looking for feedback and one bit of info.

First the questions:
Is finalize_body the right place to override to do this? If so, how can 
I make sure it's gone through the view already?


Now feedback:
Catalyst::Plugin::Static::Real? Catalyst::Plugin::Static::ToFile? 
Something else?

Per file/controller assignment of static-ness? Per directory? Both? 
Something else?

Should it be coupled with facility to unlink/rm/clear the files and 
directories it creates or should that fall outside the scope?

Anything else?

Thanks!
-Ashley




More information about the Catalyst mailing list