-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Luke,
thanks for your answer. > I'm confident there's an easier way; just the way you're using the > autoloader there seems unecessarily complicated. Why are you even > using autoloading? Why don't you just hard-code the invalidator > name, and use normal 'require' or something similar? Because the invalidator should be pluggable, means that people should be able to deliver their own version of the invalidator in their own modules and just configure my terminus to use their implementation of the invalidator. So as far as my experience goes, I can't simply require a file that is delivered by modules, that's why I started using the autoloader, which walks through all lib dirs of the modules and loads the found one. Or I'm wrong with my understanding how lib code is loaded? Distributing the terminus in an own module works well and it's also loaded after being configured in routes.yaml. But what's about additional code for that terminus, that should also be loaded and plugged in based on an own configuration option for that terminus? ~pete -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iEYEARECAAYFAlFmXSMACgkQbwltcAfKi39D0ACeJRwB4RZmTJaCDCV7mLY+8VNn waMAoLdTde6PyiYSQfjaCihaCtVKa3o0 =VJLu -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
