On Thu, Feb 17, 2011 at 12:16, Russell Jackson <r...@csub.edu> wrote: > On 02/15/2011 05:37 PM, James Louis wrote: > >> in spite of this not actually being a "push" mechanism if it walks like >> a duck. it would be nice if the documentation and previous discussions >> on this were more clear or even better if it's not a "push" then the it >> should be "redefined" within puppet world. IMHO > > Actually, almost anything that is referred to as "push" is usually > implemented as some sort of pull trigged via a notification mechanism.
That seems an odd claim in general, but whatever. In the specific case of puppet we have a prototype for a "static compiler" that we are working on internally. The goal is to allow a set of files, catalog included, to be pushed out from the central server to the client, with no loss of fidelity or control. So, we are sympathetic to the requirement for a genuine push solution (which is actually push), and are working on solutions to the problem. They don't even have a roadmap date yet, though, I fear. :) Daniel -- ⎋ Puppet Labs Developer – http://puppetlabs.com ✉ Daniel Pittman <dan...@puppetlabs.com> ✆ Contact me via gtalk, email, or phone: +1 (877) 575-9775 ♲ Made with 100 percent post-consumer electrons -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-users@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
