nop has asked for the wisdom of the Perl Monks concerning the following question:
Hi. I've just started reading about
Mason and am getting interested in the technology. My early sense is Mason offers a powerful way to build modular web pages via components. Components can have perl in them, though I agree with the
assertion that too much code isn't the best idea.
I also see that Mason can interact nicely with apache::session to handle state.
Here's my question: how do folks using Mason handle application logic? I've built a hand-rolled version of CGI::Application that meets my needs and used TT2; do I do the same w/ Mason? Or does Mason have logic routing code aspects to it?
Also, can anyone offer examples / links / suggestions to using Mason in a model-view-controller design?
These are new areas to me; apologies if my question reflects that. Thanks --
nop
Here's my question: how do folks using Mason handle application logic? I've built a hand-rolled version of CGI::Application that meets my needs and used TT2; do I do the same w/ Mason? Or does Mason have logic routing code aspects to it?
Also, can anyone offer examples / links / suggestions to using Mason in a model-view-controller design?
These are new areas to me; apologies if my question reflects that. Thanks --
nop
Back to
Seekers of Perl Wisdom