ardenius

Hello Jacques1 , sorry for calling you Guru (the Guru was really large and I was confused that this is your nick). I also use a type of code generator for plain objects that comes directly out of a DB table , of course in several occasions I have to add some properties and getters and setters to them because the business logic might need those. Also I use code generators for data workers and instantiators , but I don't find this crucial , in fact I would never advise anyone that is just beginning understating OOP and MVC to use code generators before fully understands what she or he is doing.

Guru is correct stating that there is no fixed laws for how MVC must be implemented. There are three or four different “core” MVC implementations and unnumbered parallaxes. For example in the MVC implementation that I am programming more often the statement of Guru: doesn't make any sense , (I really can't understand what is the “model” in this implementation if not classes that you write by your hand , of course there are tools that helps you writing plain objects / data workers e.t.c. but code generators are irrelevant to the MVC pattern , in my point of view). Back to the question. First of all I understood what you meant by “session” but it will easier for you to adopt some other term (e.g. the life cycle of the request) because in web programming “session” has a completely different meaning. Having said that there is nothing terrible wrong with your approach. Let me just make some comments in my perspective , and having in mind the MVC implementation I write more comfortable at: Yes model also updates / creates / inserts in the data layer (that layer might be also an external web service , but yes most common it is a db). I have a question in “a specific object for use throughout the current page”. Even in active record pattern , model is not used for a specific object exclusive. Model will create any objects (or lists of them) that the controller needs. I have more minor comments but MVC is a very old way (even before we call it MVC) of separating the logic of a program in layers upon their functionality and if your implementation doesn't do something awfully weird than its ok.