Editing Model–view–controller (section)

==Use in web applications==
Although originally developed for [[Desktop computer|desktop computing]], MVC has been widely adopted as a design for [[World Wide Web]] applications in major [[programming language]]s. Several [[web framework]]s have been created that enforce the pattern. These [[software framework]]s vary in their interpretations, mainly in the way that the MVC responsibilities are divided between the [[client–server model|client and server]].<ref name="leff">{{cite conference|first1=Avraham|last1=Leff|first2=James T.|last2=Rayfield|title=Web-Application Development Using the Model/View/Controller Design Pattern|date=September 2001|conference=IEEE Enterprise Distributed Object Computing Conference|pages=118–127}}</ref> Early MVC frameworks took a [[thin client]] approach that placed almost the entire model, view and controller logic on the server. In this approach, the client sends [[hyperlink]] requests or [[form (web)|form]] submissions to the controller and then receives a complete and updated [[web page]] (or other document) from the view; the model exists entirely on the server.<ref name="leff"/> Later frameworks have allowed the MVC components to execute partly on the client, using [[Ajax (programming)|Ajax]] to synchronize data.