On 08.03.2011, at 10:01, Benjamin Eberlei wrote:
>> on IRC Benjamin explained that the magic in FrameworkExtraBundle needs
> to
>> know which action is being called in order to work. this to me just
> means
>> that instead of registering the magic in core.view it should be
> registered
>> in core.request. this way whatever data the FrameworkExtraBundle needs
>> would be configured before the controller is called, making it again
>> possible to just use some helper method to apply the annotation magic.
>
> No, i said since controller invocation uses reflection it needs explicit
> method names,
> so you cannot hook into the pre and post invocation of a controller there,
> which is
> why core.view exists.
just to clarify my point:
core.view only exists in order to reduce the number of characters that need to
be typed to a bare minimum. we have enough events that happen before the action
is called to enable some explicit method inside the controller that applies all
the magic of the frameworkextrabundle but ensures that a Response instance is
always returned from a Controller.
return $this->doMagic(array('name' => $name)); vs. return array('name' =>
$name);
regards,
Lukas Kahwe Smith
[email protected]
--
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
