PHP OOP Design Patterns: Should I Create two seperate classes for registration and form validation?

Posted by Joshua Poshua on Stack Overflow See other posts from Stack Overflow or by Joshua Poshua
Published on 2010-04-23T13:49:50Z Indexed on 2010/04/23 13:53 UTC
Read the original article Hit count: 233

Filed under:
|
|
|
|

So here's my problem: I have two types of registration, registration A and registration B, each will have some of the same fields and some different fields. I was going to create abstract class registration and both A and B would have their own classes that extend from registration. My question is, should I create a seperate Validation class with seperate A and B validation classes that extend? or is there a better pattern to use for something like this?

Thanks

© Stack Overflow or respective owner

Related posts about php

Related posts about oop