If I understand you correctly (the code == 1000 words) we did a similar
thing for a dynamic XML source - just made a new page for the component's
data source and returned the XML from onActivate.
Chers,
Nick.
Josh Canfield wrote:
I thought I had a pretty slick dynamic image component using
Yep, sounds like you understand correctly. I yanked the onImage event out of
the component and put it into the onActivate of a new page (ViewImage) and
replaced the actionlink with a pagelink. That works great and it also has
the added benefit of providing a better browser caching experience
I thought I had a pretty slick dynamic image component using the examples
from the list and wiki. Recently I noticed a performance problem and tracked
it to excess database access. It seems that whatever page I embed the image
component in gets fully re-loaded when the onImage action is trigged.