On 2/21/11 3:03 PM, Lukas Kahwe Smith wrote:
Aloha,So picking up another discussion that spawned in the eager response discussion [1]: removing the Response service Right now it gives a false sense of control, furthermore it gives the appearance that it would be a best practice to inject the Response service, which causes all sorts of trouble since its prototype scoped. As a result I propose to remove the Response service. Meaning where ever we currently do $this->container->get('response') would now need to write new Response() with the given use statement at the top of the file.
Done here: https://github.com/symfony/symfony/commit/d94acd85f9aee2342c7ec381d7fdd66aea1eafef Fabien
regards, Lukas Kahwe Smith [email protected] [1] https://github.com/fabpot/symfony/pull/744#issuecomment-791042
-- 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
