Update Type is used then to indicate to the Views that the Model has changed - a Push notification , I think you mentioned,
as it tells the View exactly what has changed, rather than a Pull notification , which just tells the View that it has changed.
Should this also be part of the Controller ?
I thought the Controller would be responsible also, for telling the View of changes ?
Do you see any problem in merging the DataAccessFacade and the Model as you have it ,
to avoid replicating all those methods?
Originally posted by Eugene Kononov:
Your model can keep a reference to your DataAccessFacade to invoke its (facade's) methods, that's perfectly fine and logical.
Somehow I don't see the function of having a separate "model" and "facade". I've used the facade as the application level model.
but I don't like the sound of having a javax.swing.TableModel (or whatever it is) be an application level "model" as it pretty much dictates the use of a table and a GUI.