On 11/21/10 4:41 PM, Lukas Kahwe Smith wrote:
On 19.11.2010, at 20:12, Lukas Kahwe Smith wrote:
first up to make this all worthwhile you need to use a model which
jordi and I called "pull templates" during our symfony live
presentation. that is the work done inside the controller is the
bare minimum to figure out what template should be loaded first. so
for example you will figure out that the requested document exist
in the database, but you dont start fetching all sorts of expensive
related content.
so essentially twig could process blocks inside the templates in a
different order than like they are actually defined in order to
more quickly be able to push out content. the blocks would each
"pull" in the content that they need, thereby delaying expensive
calls as long as possible.
just wanted to make clear: the above mentioned strategy is also
important to benefit from ESI caching. i guess therefore it should be
a "best practice" to pass a model and/or repository instance in order
to easily fetch the data that is needed for display in the view
layer.
What do you mean? I don't see how streamed responses and ESI caching are
related here?
Fabien
regards Lukas Kahwe Smith [email protected]
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en
