Hi Tim On Fri, 2011-05-20 at 11:28 -0400, Timothy Appnel wrote: > > What in C::A::P::REST would require you to do that? > > I work with Melody, a community for of Movable Type and we already > have a couple of dozen of app modules and probably a hundred run > modes. We need a dispatching mechanism in front of CGI::App and not in > it to avoid loading anything we don't need. [This is not the case > currently with the mess we inherited, but that is where we are > committed to going with the code.]
It's sad to hear you refer to that code as 'the mess'. I often wonder where Melody is heading. That complexity is precisely why I'm so wary when people suggest replacing the current wiki 'with something written in CGI::App'. If they know what they're talking about, fine, but if not... My biggest project was written before I learned of CGI::Application::Dispatch, so I have some understanding of what you're going thru. Once my app was running, featureitis took over. Some pages had 1,500 or more links. Ok, so they're automatically generated lines of output (uni staff list search result), but it's a PITA. Now, I never write an app without C::A::D, and it's always combined with MVC style module design. -- Ron Savage http://savage.net.au/ Ph: 0421 920 622 ##### CGI::Application community mailing list ################ ## ## ## To unsubscribe, or change your message delivery options, ## ## visit: http://www.erlbaum.net/mailman/listinfo/cgiapp ## ## ## ## Web archive: http://www.erlbaum.net/pipermail/cgiapp/ ## ## Wiki: http://cgiapp.erlbaum.net/ ## ## ## ################################################################