Because those things represent internals of the configuration that are
subject to change, and we don't want end users becoming dependent on them.
They are protected, because they may be needed for subclassing, where the
subclass assumes some greater risk than an end user of the API.
Christopher L Tubbs II
On Wed, Jul 16, 2014 at 9:43 PM, Josh Elser <[EMAIL PROTECTED]> wrote: