[Catalyst] Caching problem?

[Wade.Stuart at fallon.com]

>
> It's a little bit awkward, but it could easily be made to happen
automagically
> (e.g. with -Request(NoCache SomethingElse) in the 'use Catalyst' line),
it's
> just there hasn't been much call for it so I didn't worry too much.
>
> Alternatively, we could go with the "all plugins in one namespace"
approach
> and have a 'plugin_for' classdata thing in each Plugin that says whether
it
> should end up in the @ISA for the appclass, request class, response class
etc.
>
> For 5.5 I concentrated on getting the hooks in there for nice stuff
later;
> actually writing the sugar was left until we had some use cases to write
it
> against. Now, apparently we have one - what does everyone think?
>
> > At least with the ugly namespace plugin, it layers with other plugins
> > like itself just fine.
>
> Right until one of them needs to overlay no_cache. namespace-stuffing
plugins
> are *always* bad news. Try mixing multiple things out the
Class::DBI::Plugin
> namespace if you want a good demonstration of why ...
>


Well I think it is very useful (I use some form of it on almost every app I
make),  but the issue is it is almost _never_ useful to set the default on
all pages served.  There needs to be simple logic allowed such as
"if not /^static/"...  I think we will be in a worse place if we hand out a
"turn all caching off" flag to people.  They need to be able to understand
what portions of their app it makes sense for and what ones it does not.