Timeline for MVC and RESTful API service
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 14, 2016 at 13:07 | comment | added | VoiceOfUnreason | The program/robot connecting to the service would presumably manipulate the model directly - why would it need a view? | |
| Jul 14, 2016 at 8:16 | comment | added | simon | I've mixed web requests with an architectural pattern to more easily illustrate what bothers me in the concept as a whole. You're saying: "The collection of widgets in the browser are the view" - then I rephrase: what if there is no 'browser' in a human scense? What if it's another robot connecting to the service? If JSON and HTML are the representation of state, then 'a message' or 'DTO' is a transport for state representation. So where does 'a view' come in place then? You've confused me even more with your answer. | |
| Jul 14, 2016 at 1:50 | history | answered | VoiceOfUnreason | CC BY-SA 3.0 |