But how would you do that without some sort of event-handling mechanism? Would you have the framework call some sort of result handler between each message?
I suppose that wouldn't actually be that hard to add to the loop that handles the broadcasts in the first place... but it would have to be based on a config flag so that code based on the current behavior isn't broken, wouldn't it? I guess the other thing that occurs to me is that it could be done with an AOP afterAdvice since MG 3+ is already dependent on ColdSpring... it may be possible to bundle the config for the controller method interceptor into the default MG config. But it would still have to use a config flag to avoid breaking code based on the current behavior. Or we could add an argument to the addResult() method that defaults to "now" but has an option for "after"... that wouldn't break anything but it would be possible to start using it from that point forward. J On Jul 27, 2011, at 1:32 PM, Sean Corfield wrote: > +1 > > On Wed, Jul 27, 2011 at 6:54 AM, Dennis Clark <[email protected]> wrote: >> Ideally the addResult() would not perform the redirect itself, but instead >> flag the framework to perform the redirect immediately after the controller >> method call has returned. That way, any processing that follows the >> addResult() would still occur, but none of the event processing that >> normally follows the call would be performed. -- 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
