＋设为首页 ＋添加到收藏夹
this article is the first of two that examine in depth the origins of the model-view-controller (mvc) design pattern and its misapplication to servlet framework architectures. the purpose of this first piece is threefold. first, it attempts to provide an accurate description of the problems brought about by mvc in servlet middleware. second, it suggests techniques and strategies for coming up with a new design, one better suited to the needs of servlet infrastructure developers. third, it offers an example of a completely new, nonderivative pattern we might use moving forward. the second article backs up my assertions by introducing and exploring a reference implementation of the new design.
part one: history of the mvc pattern 【程序编程相关:Practical JSTL, Part】
ultimately, my goal with these two articles is to convince the servlet middleware community once and for all to put the dark days of mvc behind us and to lay the groundwork for completely new, nonderivative servlet middleware architectures that better address our common needs. please bear with me; i wouldnt write a piece about mvc in the servlet tier unless i believed it was a funeral dirge. 【推荐阅读:Practical JSTL, Part】
tracing the historical origins of the model-view-controller pattern is not a difficult thing to do. the man who brought us mvc has published historical documents that date back to 1973, when object-oriented programming was still being conceived and scientists were only beginning to explore the concepts of "distributed, communicating components." (see reenskaug, trygve, "the history of mvc.") 【扩展信息:Fighting Against Com】
we begin with a historical account of mvcs origins in the early 1970s and its subsequent use as a pattern for thick-client ui component frameworks.
following the paper trail back to the early days of object modeling is instructional in two ways. first, it serves as a reminder that the problems we face today in distributed computing are by and large the same ones faced by computer scientists from three decades ago — in other words, the proverbial wheel is still in dire need of reinvention. second, it shows us how much we still have to learn about simplifying complex systems.
oslo norway, 1973in august of 1973, dr. trygve reenskaug, while working for the central institute for industrial research in oslo norway, wrote a paper called "administrative control in the shipyard," which he presented at the first international conference on computing applications in shipbuilding that autumn. in his paper, reenskaug analyzed the modern shipyard as an information system. in this exercise, he identified many of the technical and social complexities inherent in shipyards and suggested several techniques that could be used while describing the system. his goal was to reduce the overall complexity so the shipyard could be more easily modeled in a computer application.
... 下一页