Question

so far the syntax is not the problem but my question is more about better understanding OOP

I am creating a class called “user” which should describe a user. typically such class would set user variables and retrieve them

would that class have a method for signingup a new user as well?
how about login?

if not ..how would I structure it?

should “signing up” be another class? in which case wouldn’t the resulting object be a “user”

same goes for the a login class…

sorry for the novis question….just trying to wrap my head around OOP.

thanks for the help 🙂

Answer 1

Most PHP OOP applications would use a model-view-controller (MVC) approach to solve this, with your user class being the ‘model’ and a ‘controller’ class providing business logic that interacts with your user class, like ‘signup’ or ‘login’. The ‘view’ part refers to the presentation code (a mix of PHP / HTML) that gets output to the browser.

A controller approach would look something like this:

class UserController {

    public function signup($userDetails) {
        // create a new user
        $user = new User();
        $user->name = $userDetails['name'];
        $user->username = $userDetails['username'];
        $user->password = $userDetails['password'];
        $user->save(); // Save to database, for example
    }

    public function login($username, $password) {
        // check the user exists and log them in
        $user = new User();

        // query database for a user with these credentials, for example
        if($id = $user->find($username, $password)) {
            $_SESSION['user'] = $id; // Save the ID to the session for future use
            return true;
        }

        return false;
    }

}

This is just a really basic example, but generally you don’t want to mix your application logic (actions such as login or signup) with your domain logic (which should just concern managing your data).

A good article on MVC in PHP can be found here: http://oreilly.com/php/archive/mvc-intro.html