[cgiapp] Re: CAP::Forward RFC (was Re: [cgiapp] ANNOUNCE: AnyTemplate 0.10_02 developer release and RFC)

[Mark Stosberg <suppressed>]

On 2005-07-25, Michael Graham <suppressed> wrote:
>
>> >     * should the 'forward' method be in its own plugin so that anyone
>> >       can use it?
>>
>> I think it should be either it's own plugin, or moved to the C::A core.
>> It doesn't really have anything to do with templates.

Yes it does. Template auto-naming is the only real use-case we've come
with for it it so far. 

So my reasoning is: "keep it close to the template system until another
use for it appears". However, it someone wants to do the work now to
seperate it out, go ahead. 

> I'm kind of leaning this way myself.  I'm happy to package it up as
> CGI::Application::Plugin::Forward if there are no objections.  BTW, is
> 'forward' the right method name?

forward() works for me. Catalyst uses the same name for a similar
concept.



---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed