The Model represents application state. The View displays the application state. The Controller captures user gestures and selects the View.
In a conventional "desktop" MVC application, the View may connect to the Model in order to display the state in "real-time". In remote applications, including Web applications, MVC is usually moderated by the Layers pattern, so that the View and the Controller interact and the Controller and Model interact, but the View and Model do not interact. V <-> C <-> M <-> (persistent store) -- Ted Husted, Husted dot Com, Fairport NY US -- Developing Java Web Applications with Struts -- Tel: +1 585 737-3463 -- Web: http://husted.com/about/services Graham Lounder wrote: > > Hi all, > > I'm starting to rethink my current code structure. One of the question I came up >with is where the application state is supposed to be. Currently I have a bean which >holds my state in the session. If I moved this application to a new client, the >state bean could end up in the database. So my question is what is appllication >state considered, model, view or controller? > > My guess would be model, and that you just save it in the session instead of the >database because it is faster for web applications. > > Any ideas? > > Graham -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
