On 01.08.2011, at 18:34, Jeremy Mikola wrote: > On Mon, Aug 1, 2011 at 9:16 AM, Lukas Kahwe Smith <m...@pooteeweet.org> wrote: > > On 01.08.2011, at 18:07, Jeremy Mikola wrote: > > > <parameters> > > <parameter key="my.service.enabled" runtime="true" /> > > </parameters> > > > > Kris Wallsmith suggested using a different attribute: > > > > <parameters> > > <parameter key="my.service.enabled" freeze="false" /> > > </parameters> > > the main purpose of this would be to prevent inlining optimizations? > > regards, > Lukas Kahwe Smith > m...@pooteeweet.org > > I suppose these technically these definitions don't have to exist. Either way > I have to merge in runtime parameters over the frozen parameters in the > dumped container. > > Although, actually having definitions means that we can catch invalid > parameters references (for runtime params as we do existing ones). When Kris > and I were discussing this, I believe we were thinking of just excluding > these parameters from the FrozenParameterBag and ensuring they get plucked in > from our runtime datasource.
well if the issue isnt that parameters get inline otherwise, then why not simply define them as null and then having some services listening (is there a kernel load event?) to overwrite them with the dynamic values. regards, Lukas Kahwe Smith m...@pooteeweet.org -- 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 symfony-devs@googlegroups.com To unsubscribe from this group, send email to symfony-devs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
