> I haven't tried it yet, but it definitely looks useful. I'm a fan of the
> global dispatcher myself, but I can see the appeal of this approach as
> well. My only complaint is the name.
I guess by global dispatcher you mean C::A::Dispatch. I wonder if
they could be used together. I was personally going to create a
mod_perl handler similar to yours in C::A::Dispatch. However instead
of dispatching directly to runmode, I would just forward the request
to the right class. Then let CAP::Attributes take over from there.
Maybe have something like CGI::Application::Dispatch::Table(your
method) and CGI::Application::Dispatch::Attr. Just a thought.
>
> It doesn't describe what it does but rather describes an implementation
> detail. Maybe
>
> CAP::AttributeDispatch
> CAP::SubDispatch
> CAP::MethodDispatch
>
> Not that those are much better :)
Hah! This was the major reason I'm not putting it on CPAN yet,
because of the dumb name. I just couldn't think of anything better.
Those are certainly much better than the name now. I should use a
name like C::A::P::ThisModuleSucks to force me to change it next time.
--
Jason Yates
suppressed
---------------------------------------------------------------------
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
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.