On 24.02.2011, at 10:32, Johannes Schmitt wrote: > I'm not sure if changing the default scope to "request" actually solves the > problem because sooner or later people will have to learn scope anyway, so > imo it would probably be best to have something in the documentation (best > with some graphics, not only text if that is possible).
Well I would say "later" is better here. > Fabien has mentioned this in another thread. At the moment, we can throw an > error if people are doing something potentially wrong; by changing the > default scope to request that would not be possible anymore. Its really only a performance thing (and quite an edge case if you ask me) and for that we might eventually provide some kind of tool to see which services are marked as scope != container. 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
