On 27.10.2010, at 08:10, Fabien Potencier <[email protected]> wrote:
> On 10/27/10 1:30 AM, Jordi Boggiano wrote: >> On Wed, Oct 27, 2010 at 12:23 AM, Lukas Kahwe Smith<[email protected]> >> wrote: >>> Yet another approach is going with the Agavi approach of having a "real" >>> view layer inbetween the controller and the templates. >> >> We discussed this to death already so I won't go over it again, but to >> me this is the only sane approach. The rest will just be dirty hacks. >> I don't want to go all the way to the Agavi model and have mandatory >> view classes though, but if you could have a default view class that >> handles json/xml/blah in a relatively sane way. Then you could have an >> optional override of that class when needed if you need custom logic. >> That will however require some heavy changes in the way actions are >> processed imo. > > Read my answer to Lukas. > > This is already possible natively and very simple to use. thinking about my other issue with xmlhttprequests and controllers that do redirects, i am beginning to realize that this could also be solved if such redirects would be implemented in the view layer. regards Lukas -- 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
