Feature #3291
Cacheable viewhelpers
| Status: | Needs Feedback | Start date: | 2009-05-14 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | - | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Has patch: | No |
Description
we need a concept for cacheable viewhelpers
Related issues
History
#1 Updated by Sebastian Kurfuerst about 4 years ago
- Tracker changed from Feature to Story
#2 Updated by Sebastian Kurfuerst about 4 years ago
- Tracker changed from Story to Feature
#3 Updated by Christian Müller over 3 years ago
- Status changed from New to Needs Feedback
- Has patch set to No
Isn't that obsolete with the Fluid caching as is?
#4 Updated by Bastian Waidelich over 2 years ago
Ha, just stumbled upon this one ;)
Christian Mueller wrote:
Isn't that obsolete with the Fluid caching as is?
"Fluid caching" is the wrong word. It's rather a "compilation": Fluid templates get compiled into PHP code with static snippets. Depending on the ViewHelpers, such a compiled template can still take a while to render. Thus cache VH would still make sense.
Here the basic one I created today:
https://gist.github.com/4168523
But I'm not sure, if it makes sense to include such VH to the distribution.
It probably makes more sense to add such behavior to the View itself in order to be able to cache partials/sections (see #43457)