On 12/19/05, Ron Savage <[EMAIL PROTECTED]> wrote: > Are you thinking of: > > $url_1 = Some::Plugin -> root_url(); > $url_2 = Some::Other::Plugin -> root_url(): > $config_1 = $self -> config($url_1); > $config_2 = $self -> config($url_2); > > in order to manage multiple plugins/configs?
I think what Mark has in mind is a system where any non-config plugin can depend on a standard place to find configuration info. For example, The session plugin requires you to configure things using the session_config method. However, if there was a standard configuration system in CGI::App, then the Session plugin could look in $self->config for Session configuration information as well (meaning the user will not need to call 'session_config'). Currently, plugins can't know if the user is using a config plugin, or what the interface of that plugin is, so there is no way to automatically look into config objects. Now what a call to $self->config actually does behind the scenes can be left up to the actual configuration plugins. It could read the info from an XML file, or pull it from a database, or just provide it from some global perl configuration variables. The important bit is the standard API that can be used to retrieve the configuration information. Cheers, Cees --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/[email protected]/ http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2 To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
