If I understand your question correctly, I would recommend a broadcast message that cached the necessary data (if not in session, then query and add to session) and output the necessary HTML, then add that broadcast to the broadcasts block of any event that needed it.
If you wanted to strictly separate Model and View, then call the cache broadcast message and also add a view to the views block that adds the correct view to the current event. In either case, it's not a separate Controller action, it's a reusable broadcast message or a reusable broadcast message + a reusable view message. <broadcasts> <message name="getCachedNav" /> </broadcasts> <views> <include name="navBar" template="dsp.cached.nav.cfm" /> <include name="body" template="dsp.main.body.display.cfm" /> </views> Something like that. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "model-glue" 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/model-glue?hl=en For more about Model-Glue, check http://www.model-glue.com . -~----------~----~----~----~------~----~------~--~---
