- 上一篇：ASP.NET概述英文文献和中文翻译
- 下一篇：B/S/Browser/Server结构英文文献和中文翻译
translate them automatically byte code of Java.
Thus, the visitant that is the website requests a JSP page, under the condition of it is not knowing, an already born, the Servlet actual full general that prepared to edit and translate completes all works, very concealment but again and efficiently. The Servlet is to edit and translate of, so the code of JSP in the web page does not need when the every time requests that page is explain. The engine of JSP need to be edit and translate after Servlet the code end is modify only once, then this Servlet that editted and translate can be carry out. The in view of the fact JSP engine auto is born to edit and translate the Servlet also, need not procedure member begins to edit and translate the code, so the JSP can bring vivid sex that function and fast developments need that you are efficiently.
Compared with the traditional CGI, the JSP has the equal advantage. First, on the speed, the traditional procedure of CGI needs to use the standard importation of the system to output the equipments to carry out the dynamic state web page born, but the JSP is direct is mutually the connection with server. And say for the CGI, each interview needs to add to add a progress to handle, the progress build up and destroy by burning constantly and will be a not small burden for calculator of be the server of Web. The next in order, the JSP is specialized to develop but design for the Web of, its purpose is for building up according to the Web applied procedure, included the norm and the tool of a the whole set. Use the technique of JSP can combine a lot of JSP pages to become a Web application procedure very expediently.
B.原文的翻译
JSP的机制
要理解JSP怎样联合以上各种所提到的技术的优点，从而轻而易举地实现各种效果，用户必须首先了解“组件为中心的网页开发”和“页面为中心的网页开发”的区别。论文网
SSJS和ASP都是在几年前推出的，那时网络还很年轻，没有人知道除了把所有的商务、数据和表达逻辑统统堆进原始网页中之外还有什么更好的解决方法。这种以页面为中心的模型容易学习并且得到相当快速的发展。然而，随着时间的推移，人们认识到这种方法不适于构建大型的、可升级的Web应用程序。在脚本环境中书写的表达逻辑被锁在页面内，只有通过剪切和粘贴才能被重用。表达逻辑通常和商务及数据逻辑混在一起，这使得当程序员试图改变一个应用程序的外观而不想破坏与之紧密结合的商务逻辑时，应用程序的文护就变得十分艰难。其事实上，企业中可重用组件的应用早已经很成熟，没有人愿意为它们的应用程序重写那些逻辑。HTML和图形设计师把它们的设计的实施工作交给了Web编写者，使他们不得不加倍工作—— 常常是手工编写，因为没有合适的工具可以把服务器端脚本与HTML内容结合起来。简而言之，随着Web应用程序的复杂性不断提升，以页面为中心的开发方式的局限性变得明显起来。
与此同时，人们一直在寻找建立Web应用程序的更好方法，组件在客户机/服务器领域流行起来。JavaBeans和ActiveX被“快速应用程序开发”(RAD)工具发行商推广给Java和Windows应用程序开发者用来快速开发复杂的程序。这些技术使某领域内的专家可以为本领域内的垂直应用编写组件，而开发者可以直接拿来使用而不必掌握这一领域的专门技术。