MVC Best place to put the caching

[whisher]

Hi.
What's the best and suitable place to put the caching, should it go into the viewer, or the model, or the controller ?

Thanks in advance.

Bye

[AnthonySterling]

It would depend on what you're caching, no other entity should be responsible for the functionality of another.

IMO, of course.

<?php
$model = new CachingModel();
$view = new CachingView();
?>

[Amenthes]

There was a similar thread not long ago:

http://www.sitepoint.com/forums/showthread.php?t=637597

[Ryan Wray]

This is something AOP is great for. Unfortunately, I believe (could be wrong) the various PHP AOP implementations leave a lot to be desired.

[whisher]

It would depend on what you're caching, no other entity should be responsible for the functionality of another.

IMO, of course.

<?php
$model = new CachingModel();
$view = new CachingView();
?>

I'm caching a result (object) from a query.

$model = new CachingModel(); 

If you mean put it in the controller I disagree
to the controller doesn't mind if data are cached or not
IMHO

I took a look to Amenthes link

so I agree with Mastodont

Should the caching be done in the view?
It depends on what do you want to cache.
- db query -> cache in model
- part of page -> cache in view or model
- whole page -> cache in view

@Ryan Wray interesting

Bye.

[mrgilb]

Are we talking caching in a folder or memory?

[whisher]

folder