Brice wrote: >> > > Each time an agent contacts the master, rebuild known_resource_types > > from scratch (using cached copies of the ASTs for the relevant files). > > > There's another con, you'll keep in memory n copies of the AST where n > is your max concurrency (thanks to the way the GC works). > I don't really know how much memory we're talking about, maybe it's > something we should not care about. >
Is this necessarily the case? If the ASTs are read-only (as they should be, though possibly aren't) they could be shared, no? Paul wrote: > It sounds to me like we have a decent consensus for Proposed Solution II > (restrict the contents of autoloaded files) with the caveat that if we're going > to make the changes in version n, it would be nice to issue deprecation > warnings in version n-1 for instances where the classes inside a file don't > fit the naming requirements. The consensus position also had option I (rebuild the TypeCollection for each compile) as an adjunct. > Would anyone object if we slid the deprecation warnings into the next 2.6 > point release (probably 2.6.3 I'm guessing), so that we can do the full > solution in 2.7? I'm for it. -- M ----------------------------------------------------------- The power of accurate observation is commonly called cynicism by those who have not got it. ~George Bernard Shaw ------------------------------------------------------------ -- You received this message because you are subscribed to the Google Groups "Puppet 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/puppet-dev?hl=en.
