Perhaps I should just say separation of presentation from logic. The web is certainly different from traditional, rich client UI but I think the roles can still be identified such as the HTML page on the client being the view and the Servlet being the controller and the data objects / model objects being the model. The principles of MVC hold in that the view should be replaceable by connecting the model to a different controller and in turn this can get connected to a different view. In this case, if the Servlet is just acting as a controller go between, pushing data into a HTML page and then pulling the response to that data from the next request to push the next lot of data then it is still kind of controller shaped in spite of lacking any direct way to listen for data on the client (albeit AJAX could provide some loose ability to do so). If the application follows this design the same model objects could be connected to a different controller that displays the data in say a Swing or JavaFX application. In that sense you still have the ability to interchange views.
-- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
