Re^2: Understanding Catalyst

In this application I did not use a database, I used cookies and the $c->session hash to manage everything, would it be more appropriate to put all the manipulations inside the Model instead of the controller?

Comment on Re^2: Understanding Catalyst

Replies are listed 'Best First'.
Re^3: Understanding Catalyst by locked_user sundialsvc4 (Abbot) on Oct 04, 2015 at 00:45 UTC
I’m not sure that the MVC paradigm really addresses that concept very well. If the application has no persistent storage, I’m not sure if one would say that it has a Model. However ... “there are no absolutes.” MVC, like everything else, is a guideline not a mantra. If you have developed something that works cleanly for you, I would not redesign it for the sake of philosophy. `:-)` Others may weigh-in with differing opinions.
Re^4: Understanding Catalyst by Your Mother (Archbishop) on Oct 04, 2015 at 18:42 UTC
Model != Storage. Model == Data. Google search API is a model, for example. A weather service is a model. `sub d10 { 1+int(rand(10)) }` is a model.	[reply] [d/l]
Re^5: Understanding Catalyst by QuillMeantTen (Friar) on Oct 05, 2015 at 06:31 UTC
In your example, shouldn't the sub d10 live in another file than the Controller/(Root\|whatever).pm?	[reply]
Re^6: Understanding Catalyst by Your Mother (Archbishop) on Oct 05, 2015 at 11:32 UTC
Re^7: Understanding Catalyst by Anonymous Monk on Oct 05, 2015 at 21:49 UTC
Some notes below your chosen depth have not been shown here