On Sun, Feb 20, 2011 at 5:58 PM, Lukas Kahwe Smith <[email protected]>wrote:
> > > Oh, I wasnt suggesting to remove it. I was suggesting to always notify > core.view and to let core.view decide if it needs to do anything. Right now > core.view is only triggered if a non Response is returned. > I think if a controller returns a response, the opportunity for core.view to be triggered has passed. I'm no expert, but I believe the "view" event is all about turning some data into response content, whether the controller does that internally (e.g. render() method to build a response) or an event handler does it. I agree it can be inconsistent that the event is sometimes triggered and sometimes skipped, depending on how/which controller serves a request, but if a controller returns a response, the next appropriate event is core.response IMO. -- jeremy mikola -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" 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/symfony-devs?hl=en
