[quote]Depedants don't have caching themselves. Cache is always held by the top level asset, so the answer would be "yes". And yes, it is more effective for complex implementations with nesting. It is built so editors can be 100% sure that a particular URL is now showing the correct content. The admin tool is useful to set things up so that particular assets are always cleared no matter what the URL or where they are nested.
Recache relies on assets actually being loaded during the page build. The admin tool could do it, but it would basically just do a request for _reache on all page URLs.
Right now, they work differently. I don't think the can both work like _reache because of the functionality I described above, but the admin tool could have an option to work like _reache so you have both options.[/quote]
Hi Greg,
This sounds quite interesting to me. Do you mean, for example, a nested asset listing page without a web path would never be cached?
Thanks,
Robin
A nested asset is not a dependent of the main asset, so it is still cached as normal.
More information of dependent assets can be found here: http://forums.matrix.squiz.net/index.php?showtopic=6508
[quote]A nested asset is not a dependent of the main asset, so it is still cached as normal.
More information of dependent assets can be found here: http://forums.matrix.squiz.net/index.php?showtopic=6508[/quote]
Thanks for the reply. I am wondering since the nested page doesn't have a web path how _nocache works as you said
[quote]Recache relies on assets actually being loaded during the page build. The admin tool could do it, but it would basically just do a request for _reache on all page URLs.[/quote]
I am just curious about that. :P’ /> <img src=‘http://forums.matrix.squiz.net/public/style_emoticons/<#EMO_DIR#>/tongue.gif’ class=‘bbc_emoticon’ alt='
Sorry didn't see your reply. Basically it was Squiz, who turned off caching on our test bed without telling us. :lol: