Ahh. Yes, definitely more a benefit when there are multiple events using a controller method. Which, by the way, is one of the single greatest powers of Model-Glue (or any Implicit Invocation framework).
On Wed, Aug 31, 2011 at 7:51 AM, Rawlins <[email protected]> wrote: > Also, I expect people get a benefit out of the <result /> approach when you > have reusable handler methods that get called by multiple events. > > I tend to follow a convention approach of having 1 controller method per > event and no more, so the action upon a given 'result' is always the same. > > -- > 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 > -- 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
