Looking at the problems resulting from us putting facts in the get request, e.g. #2855, makes me again think this is the wrong approach.
This ability only exists because, when running multiple servers without client binding, there's a chance that the facts get sent to a different server than the catalog is retrieved from. I'm thinking that it might be a better idea to solve this problem than to hack around it. The main solution I'm thinking of is essentially requiring some kind of shared back-end or requiring a shared cache such as memcached. A shared cache with memcached should be pretty close to trivial - just another terminus type. This obviously adds another dependency, but only in those cases where you 1) have multiple masters, 2) don't have client binding to an individual master, and 3) aren't using some common back-end (one of which will be available from us with this information by the next major release). Is this a reasonable approach? It's obviously not sufficient for 0.25.2, but I think it's a better long term direction. -- I went to a restaurant that serves "breakfast at anytime". So I ordered French Toast during the Renaissance. -- Stephen Wright --------------------------------------------------------------------- Luke Kanies -|- http://reductivelabs.com -|- +1(615)594-8199 -- 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.
