I just read the Head First - Design patterns and aftrer the Compund Pattern chapter(on the MVC) some question just raise in to my head.
I design the URLyBird 1.3.3 and on the client side I manipulate data but I get this data(s) from the server side, responsable for the data "transport" is in my case the controller - he interacts whit the server, gets the information and packs it in to a model(or it changes the model).The model informs the view about the changesadn so on.
In the Head First - Design patterns on the Compound Patterns , MVC I found :
*The controller implementes the behavior for the view
*The model implements the application logic - the application logic is the code that manages and manipulates the data.
I think this can be true if I have only a pure MVC whitout a relation with an existing system.If you integrate your MVC in to a system then the controller is the "link" between your applicaion(MVC) and the rest of the system.Basic I have somethig like:
user -> view -> controller -> system
if the user interact with the view and :
system -> controller -> model -> view
if the system react(responds).The same logic I found in Max book.
I know that ther are many ways to implement (correct) the MVC pattern but is wrong to make the controller responsable for the "data" transport ?
[ June 01, 2005: Message edited by: Mihai Radulescu ]
I design the URLyBird 1.3.3 and on the client side I manipulate data but I get this data(s) from the server side, responsable for the data "transport" is in my case the controller - he interacts whit the server, gets the information and packs it in to a model(or it changes the model).The model informs the view about the changesadn so on.
In the Head First - Design patterns on the Compound Patterns , MVC I found :
*The controller implementes the behavior for the view
*The model implements the application logic - the application logic is the code that manages and manipulates the data.
I think this can be true if I have only a pure MVC whitout a relation with an existing system.If you integrate your MVC in to a system then the controller is the "link" between your applicaion(MVC) and the rest of the system.Basic I have somethig like:
user -> view -> controller -> system
if the user interact with the view and :
system -> controller -> model -> view
if the system react(responds).The same logic I found in Max book.
I know that ther are many ways to implement (correct) the MVC pattern but is wrong to make the controller responsable for the "data" transport ?
[ June 01, 2005: Message edited by: Mihai Radulescu ]