On Fri, 7 Sep 2001, Kyle Oppenheim wrote:
> I never really needed to deviate from the defaults. So, I'd be happiest if
> I could still simply say
>
> SetHandler perl-script
> PerlHandler Apache::Registry
that's not going to change. really.
> and have the opportunity to use the components only if I needed to. The
> difficulty we had in subclassing PerlRun was because we needed to add calls
> to methods like parse(), not to change these few options. I have a feeling
> most users don't care about how the package name is generated or how their
> code is wrapped, but I have no data to back that up ;-) .
in the new version you will be able to do any customization much easier.
>
> - Kyle
>
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On Behalf Of
> > Stas Bekman
> > Sent: Friday, September 07, 2001 8:29 AM
> > To: modperl-2.0 dev-list
> > Subject: RE: Apache::Registry family re-design
> >
> >
> >
> > Now when I think more about it, we don't really need the cooker to start
> > with, just think of lego, rather than inheritance;
> >
> > package Apache::Registry;
> >
> > use Apache::Registry::Components ();
> >
> > *handler = *Apache::Registry::Components::handler_cool{CODE};
> > *sub_wrap = *Apache::Registry::Components::sub_wrap_def{CODE};
> > *gen_package =
> > *Apache::Registry::Components::gen_package_based_on_filename{CODE};
> > *should_stat = *Apache::Registry::Components::dont_stat_file{CODE};
> >
> > 1;
> >
> > __END__
> >
> > So instead of using inheritance and waster on @ISA search, we just using
> > aliases. And if you want to craft your own Registry module, you just pick
> > the components you want from Apache::Registry::Components and alias them
> > to the known API, so the components will be interchangable.
> >
> > Later on we can write the cooker that does this for users using more
> > user friendly interface, like the cook() function I've presented in my
> > original example.
> >
> > In any case I want to generate sets of components, and once they available
> > you can use whichever methods you prefer to build your module of dreams.
> > Note that XS and Perl implementations can be crafter for each component.
> >
> > I think this approach doesn't enforce us to case anything in stone and we
> > can reuse big chunks from the existing modules.
> >
> > _____________________________________________________________________
> > Stas Bekman JAm_pH -- Just Another mod_perl Hacker
> > http://stason.org/ mod_perl Guide http://perl.apache.org/guide
> > mailto:[EMAIL PROTECTED] http://apachetoday.com http://eXtropia.com/
> > http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
_____________________________________________________________________
Stas Bekman JAm_pH -- Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide http://perl.apache.org/guide
mailto:[EMAIL PROTECTED] http://apachetoday.com http://eXtropia.com/
http://singlesheaven.com http://perl.apache.org http://perlmonth.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
