> > * Do something as Rob suggests with a pluggable dispatch architecture. > > In this case CA::Dispatch would probably become > > CA::Plugin::Dispatch, anyway. > > But C::A::D can't really be plugin since it sit's outside of C::A. Especially > in > mod_perl where it becomes you PerlHandler. It doesn't add anything to C::A, it > just handles the mapping of URL to module/rm.
Yeah, I know - but I gather Rob's got some ideas for making C::A's dispatch system pluggable, though. I'm not sold on it, but it seems like it will be an interesting discussion. I do like the idea of being able to use CA::Dispatch as a PerlTransHandler thought. ... > My preference would be to keep all the old features of C::A::D but point > people > to ways of accomplishing the same thing with the "new-way". Maybe even make > the > "old-way" work behind the scenes by using the "new-way". I'm kinda busy right > now, but I have something in my head. If I get some time today or tomorrow, > I'll > write it up the API and see what others think. Coolness! Michael --- Michael Graham <[EMAIL PROTECTED]> --------------------------------------------------------------------- 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]
