Looks pretty good. :)

I'm curious why you didn't just put the entire user object in the session?

It may also be worth mentioning that in any real app, the passwords should be hashed with the username and a salt value to keep them secure.

Ok, off-topic reply, because we're looking at IDEs again. It seems like autocomplete isn't working with constructor? Have you noticed other issues with autocomplete in your IDE, or is that really the only place it breaks?

Why not put the entire object into the session: i'm a fan of keeping the session state extremely lean. Also, by force-refreshing it on every page load, I get to pick up stuff like "this user account is disabled" in the middle of a session :-).

On hashing passwords: definitely. Editing an existing screencast is a pain, but I'll do it in the next one.

On autocomplete: it's spotty in Komodo at best. In other editors, I've seen it to be even worse (i.e. $this->txtTextBox-> would autocomplete to nothing - because the IDE is not smart enough to look up the properties of a QTextBox/QTextBoxBase/QControl/QControlBase chain).

I'm yet to find a good IDE with good autocomplete for PHP, that would deal well with a complex class structure.

Great Screencast

Now I related a voice with a smile face.

Thanks for your effort.

enzo