Form Validation Default |
05-26-2016, 09:05 PM
(This post was last modified: 05-26-2016, 09:08 PM by PaulD. Edit Reason: typo )
Personally I agree with albertleao and would never put validation in a model either. Although I think a lot of these differences come simply from different interpretations of what the different parts of the MVC model are for. But since this is only a pattern people can of course adapt it, interpret it, or use it in any way suitable for the needs of the project in hand.
I often wonder if the MVC pattern itself is no longer adequate or the best fit for web applications. I already use libraries as controllers really, and controllers as supervisors or front-controllers. I also use libraries for templating too, although I think of them as a presentation layer, in an attempt to modularise output and stay as DRY as possible and keep views as php free as possible. Paul. |
Messages In This Thread |
Form Validation Default - by edoramedia - 05-22-2016, 12:32 AM
RE: Form Validation Default - by skunkbad - 05-22-2016, 12:40 AM
RE: Form Validation Default - by cartalot - 05-22-2016, 12:06 PM
RE: Form Validation Default - by albertleao - 05-22-2016, 05:23 PM
RE: Form Validation Default - by cartalot - 05-26-2016, 09:49 AM
RE: Form Validation Default - by albertleao - 05-26-2016, 04:29 PM
RE: Form Validation Default - by skunkbad - 05-26-2016, 10:48 AM
RE: Form Validation Default - by mwhitney - 05-26-2016, 02:14 PM
RE: Form Validation Default - by PaulD - 05-26-2016, 09:05 PM
|