On 18.04.2011, at 17:06, Lukas Kahwe Smith wrote: > > On 18.04.2011, at 17:03, Jordi Boggiano wrote: > >> On 18.04.2011 16:06, Lukas Kahwe Smith wrote: >>> 1) #9625 service container default scope >>> This one is important to make the life of beginners easier and cannot be >>> changed later on. >>> This one would ideally be handled by either Kris or Johannes. >> >> What about services that don't have the container, are they >> automatically bumped to request scope if they use the request service? > > > yes, the idea is for core to always hardcode the scope, aka everything that > doesnt have a scope atm would be hardcoded to "container". based on these > services we can then automatically determine what scope a user defined > service should have. and yes anything that injects the container and doesnt > specify the scope will be assumed to be request scope.
s/assumed to be request scope/assumed to be prototype scope as stated in the ticket. so just to clarify once more: we look at all services injected and use the least permissive scope used: aka if you have a single prototype scope dep, it will be set to prototype etc. now one open question is what happens if all services that are being injected do not have any scope set. i guess in this case we will default to container scope, aka no change. 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
