Yeah, I've always used MVC with a repository pattern for handling Model operations. The controller is still calling the operations here, and handling events tri

Yeah, I've always used MVC with a repository pattern for handling Model operations. The controller is still calling the operations here, and handling events triggered by the user. The O and E in MOVE sounds effectively the same as the C in MVC. Model objects are generally just POCOs (or POJOs, or whatever) and should not know about their storage mechanism or dealing with user events. Sounds like he's basically been doing MVC wrong, and thinks MOVE is something new, when really it's just closer to the way MVC should be done in the first place.