On 2009-11-21, at 3:00 PM, Sean Corfield <[email protected]> wrote: > > And when a redirect is used all that would have to be saved across the > redirect too... >
Right. I was only thinking that this would be useful on a do without a redirect. > It also ties views directly to controller/XML logic which seems like a > bad idea in my mind. > > Having a view displaying an optional error message, pulled from the > event objects seems much better architecture to me. Then the view > neither knows nor cares how it got there. Yeah, that makes sense. I was just thinking about this some more and realized that I'd likely set a variable into a result object in my model, return that to the controller, and put it into the event. The problem was that I'm just writing the controller and the view right now and that sent me down the wrong thought path. Thanks everyone for your responses. Cheers, Bob -- Model-Glue Sites: Home Page: http://www.model-glue.com Documentation: http://docs.model-glue.com Bug Tracker: http://bugs.model-glue.com Blog: http://www.model-glue.com/blog 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
