Re^3: Catalyst, Jifty MVCs too "expensive"...feasible alternative?

Mapping URLs to methods in your class. Catalyst has a lot of funtionality for this, as you'll see if you browse the docs. Not sure about Jifty. CGI::Application has code for using either query strings (/catalog/product.cgi?rm=show) or a more REST-like approach (/catalog/product/show).

Comment on Re^3: Catalyst, Jifty MVCs too "expensive"...feasible alternative?

Replies are listed 'Best First'.
Re^4: Catalyst, Jifty MVCs too "expensive"...feasible alternative? by stonecolddevin (Parson) on Oct 09, 2006 at 18:22 UTC
I noticed Catalyst is pretty good to go as far as that goes. I'm thinking Catalyst is the way to go for me, Jifty seems a bit restricted. I could write a base framework for the small apps in C::A, then do all my big stuff with Catalyst. Thanks for the definition :-) meh.	[reply]
Re^5: Catalyst, Jifty MVCs too "expensive"...feasible alternative? by markjugg (Curate) on Oct 09, 2006 at 21:42 UTC
URL dispatching is available with CGI::Application, it available through CGI::Application::Dispatch. That's the trend with CGI::Application: less weight built-in by default, but lots of options for extensions and plug-ins. Mark Stosberg	[reply]


Clear questions and runnable code get the best and fastest answer
	PerlMonks