On 2005-12-20, Cees Hek <[EMAIL PROTECTED]> wrote:
> 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.
Cees has done an accurate job of translating my ideas into Australian.
Thank you. An example would that this would expected to work:
$self->config('root_url');
(OK, this syntax is different than my proposal. Michael Graham talked me
into it on IRC. It's more flexible because it's not tied to an
implementation and doesn't require the whole config be loaded
at once, as a hashref would (unless you tie it).
A plugin could carve out it's own name space in the configuration file
by using a uniquely named hashref:
# a hashref of configs for C::A::P::Session
my $session_href = $self->config('cap_session');
It might not be reasonable for a plugin to expect you to have a config
variable named 'driver' used for just for them, but expecting that is
partitioned off in $ses_href->{cap_session}{driver} could be reasonable.
I'm not suggesting formally enforcing or managing any name space issues, though.
A plugin could offer that.
Mark
--
http://mark.stosberg.com/
---------------------------------------------------------------------
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]
