In an Entry archive template, I use mt:Assets to retrieve assets with one or more tags. Those assets (images) are always related to the Entry in context. I would like to know if the process of looping over all assets is slower compared to using the mt:EntryAssets container tag. With other words, is there something about the mt:EntryAssets tag that makes it faster at finding associated (embedded) images?
As the library of assets grows larger and larger over time, I am thinking that a retrieval by tag may strain the system. Probably that's nothing I have to worry about, but some facts or opinions on this would be welcome.
Reported on Movable Type 4.2
It will be much slower because <mt:Assets> does not pick up the context of the <mt:Entries> container. To see what I mean, just try:
<mt:Entries lastn="50">
<mt:EntryTitle/><br/>
<mt:Assets>
<mt:AssetURL/>
</mt:Assets>
</mt:Entries>
in an index template. The output will be quite huge.
Thanks - that's what I mean. Well I guess I'll bear that cost though, because assignment by tag is so amazingly flexible. Should the design change, thumbs can be recreated in a snap. In contrast, after embedding an image, I am stuck with it (and its corresponding thumbnail), unless I use a regex on mt:EntryBody.
Still weighting my options...