Yeah, I am sorta going down with this in the thread: Should controllers
I am wrong about this (somewhere way back I decided that MVC was just
another term for the old 3 tiered architecture, which it isn’t).
But I am seeing a lot of grey area and maybe business logic isn’t the
correct terminology. I know for a fact that business RULES (like can’t
withdraw more money than in your acct, etc) completely belong in the
model. But I am getting a little confused about the differences between
application logic and business logic and how they belong in a “rails”
I posted a question in that other thread, maybe you know answer…
Should your model (as in the M in MVC) really be isolated enough that it
could potentially be used in a complete non-web based application if
Check out the thread titled “Should controllers be “smart”?”
Michael K. wrote:
On 5/5/06, Chris B. firstname.lastname@example.org wrote:
According to the model-view-controller architecture, your business logic
should go into the controller.
Don’t put your business logic in a model like someone suggested, that is
No, that’s the entire point of having a model. Sticking business
logic anywhere else is completely and totally wrong.
Controllers are for the interaction model, Models represent your