On Mon, May 14, 2012 at 2:11 AM, Emile MOREL <[email protected]> wrote: > Daniel Pittman a écrit : > >> It would be great to improve that, from our point of view, but I >> wonder a bit: when is this a killer problem for everyone? >> >> Also, someone commented about using marshall to speed this up - sadly, >> that isn't an acceptable solution. We have had problems with Marshall >> data being impossible to transport between Ruby versions, and worse, >> causing segfaults. That means we can't use it to persist data where >> it might be read by a different version Ruby later. > > Caching catalog may not be used as a cache. We are using puppet only in > interactive mode and we use the cache to extract some data (like a kind of > report).
That is an interesting use-case, and not one I had expected - I am surprised someone is using the "cached" catalog as an API like that. What report style data do you extract? Supporting multiple cache formats is a trade-off, because there is additional complexity to identify the content to read safely, which means more code - and more code to have bugs. It sounds like you would almost be as happy to just disable the caching entirely, other than your reporting needs, yes? -- Daniel Pittman ⎋ Puppet Labs Developer – http://puppetlabs.com ♲ Made with 100 percent post-consumer electrons -- 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.
