What about making the Request object optional and default it to null. On Dec 7, 6:58 pm, Fabien Potencier <fabien.potenc...@symfony- project.com> wrote: > On 12/7/10 6:51 PM, Johannes wrote: > > >> This is one of the key points of the Symfony2 design. No main request, > >> no main response. Thanks to that design decision, we are able to manage > >> ESI easily for instance. > > > Maybe, I haven't explained this enough, but I don't want to change > > this behavior :) > > > Right now, the response is typically instantiated in the controller/ > > view. I'd like to move the response instantiation just to an earlier > > point in the stack. > > For example, we could move this to the Request (the final > > implementation may be more complex, just to get > > idea):http://pastebin.com/2LheArTE > > I don't like the coupling between the Request and the Response... but > that's just a felling. I cannot explain why ;) > > Fabien > > > > > > > > > Johannes
-- 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
