Maybe I don't understand MVC, but isn't the point to keep the M V and C separate and interchangeable? So that if you write this thing for a web page, and then later realize you'd like to write a console app, or you decide you want to use a different database, it's really easy? The User object doesn't know or care about HTML or text or whatever. There's view gunk that handles that.

So, maybe you'd have a User object, and a User::MySQL object and a User::HTML object.

And then later you write the User::Console object and the User::PostgreSQL objects.

Or am I thinking of some other acronym?

-Pileofrogs