[Catalyst] Shoot out -- Catalyst / RoR / Other MVC apps --

Perrin Harkins perrin at elem.com
Tue May 8 16:51:40 GMT 2007


On 5/8/07, Dave Rolsky <autarch at urth.org> wrote:
> There's a little more than just mapping input to a method. I think of it
> as a translation layer between how the web server presents data and how my
> model API wants it. And then there's reverse mapping, for example
> translating exceptions thrown by the model into error messages we can show
> to the user.

Both good points.  My post was over-generalized and glossed over some
things.  Your point about separating the model from the environment is
the real heart of the issue.

> One consequence of doing MVC the "right" way, though, is that you tend to
> up with rather large and complex sets of model classes.

I think it's fine for people to shortcut this and shove model stuff
into their RoR/Catalyst controller classes, as long as they understand
the trade-off they are making, i.e. it will be difficult to separate
this code and reuse it elsewhere.

- Perrin



More information about the Catalyst mailing list