:: Config_Registry (proposal)
Chapter 2

Config_Registry does not exists to supplant PEAR::Config package. It will help you to manage (one or more) application, configuration and services with only a package (class).

Applications

An application, is your user-end work. It could be a horde application like IMP, Turba, ... my SW4P, or anything else.
To register an application (see Config_Registry::registerApplication()), you have to give only: a short application name (code or handler), a long name, and the file root on your web server.

Register an application is mandatory, and should be the first step of registry operation.

You can register as much application as you want.

Configurations

A configuration is a set of application-parameters and values. I use the PEAR::Config Container as internal structure
. Its help me to propose features like:

• import external configuration data (various format: phpArray, XML, ini, ...)
• export configuration data to external resource
• read config parameter value (see Config_Registry::getParam()) in a layer level priority.
• change existing config parameter value (see Config_Registry::setParam()) in a layer.
• add new config parameter (see Config_Registry::addParam()) in a layer.
• delete config parameter (see Config_Registry::removeParam()) in a layer.
• retrieve a config parameter value (see Config_Registry::searchParam()) in a layer level priority.

And much more. See Config_Registry:: setDefaults, getConfigResource, getConfigLayer

Layer level priority means:
When searching a config parameter value, if a 'user' value exists, it will be returned first, then 'system' and finally 'default'. See PEAR/Config of PEAR core to see what i'll try to explain.

Services

Services, also named "hooks", provides a set of functionalities for communication between applications (as plugins). See Horde::Registry concept.

Its help me to propose methods like:

• determines if a hook is defined for an application (see Config_Registry::hasMethod())
• retrieves application that support a method (see Config_Registry::getHandler())
• call a specific hook for an application (see Config_Registry::callService())

continue on chapter 3 [What Config_Registry can't do]

return to [Table of Contents]