【導讀】好的可移植性，更節(jié)省投資。來自Web瀏覽器或其他HTTP客戶程序的請求和HTTP服務器上的數據庫或應用程序。Servlet的工作是執(zhí)行西門的任務，如圖所示。讀取客戶發(fā)送的顯式數據。最終用戶一般在頁面的HTML表單中輸入這些數據。然而，數據還有可能來自applet. HTTP信息包括cookie、瀏覽器所能識別的媒體類型和壓縮模。算得出對應的響應。或者不能返回HTML形式的結果，所有Web瀏覽器不能直接與數據庫進行會話。因此，我們需要Web中間層從HTTP流中提取輸入數據，與。應用程序會話，并將結果嵌入到文檔中。但是，到目前為止，HTML式最。常用的格式，故而servelt和JSP的重要任務之一就式將結果包裝到HTML中。設置cookie和緩存參數，以及其他類似的任務。然而，許多情況下靜態(tài)的結果不能滿足要求，我們需要針對每個請求生成一個。HTTP報頭，處理cookie，跟蹤會話，以及其他次類高級功能。Servlet支持常規(guī)CGI難以實現或根本不能實現的幾項功能。

　　

【正文】 ond, both countries have (or had, at that time) highly 10 unfavorable currency exchange rates against the . dollar. So, buying a specialpurpose Web server from a . pany consumed a large part of early project funds. But, with servlets and JSP, they could start with a free server: Apache Tomcat (either standalone, embedded in the regular Apache Web server, or embedded in Microsoft IIS). Once the project starts to bee successful, they could move to a server like Caucho Resin that had higher performance and easier administration but that is not free. But none of their servlets or JSP pages have to be rewritten. If their project bees even larger, they might want to move to a distributed (clustered) environment. No problem: they could move to Macromedia JRun Professional, which supports distributed applications (Web farms). Again, none of their servlets or JSP pages have to be rewritten. If the project bees quite large and plex, they might want to use Enterprise JavaBeans (EJB) to encapsulate their business logic. So, they might switch to BEA WebLogic or Oracle9i AS. Again, none of their servlets or JSP pages have to be rewritten. Finally, if their project bees even bigger, they might move it off of their Linux box and onto an IBM mainframe running IBM WebSphere. But once again, none of their servlets or JSP pages have to be rewritten. 6． Secure One of the main sources of vulnerabilities in traditional CGI stems from the fact that the programs are often executed by generalpurpose operating system shells. So, the CGI programmer must be careful to filter out characters such as backquotes and semicolons that are treated specially by the shell. Implementing this precaution is harder than one might think, and weaknesses stemming from this problem are constantly being uncovered in widely used CGI libraries. A second source of problems is the fact that some CGI programs are processed by languages that do not automatically check array or string bounds. For example, in C and C++ it is perfectly legal to allocate a 100element array and then write into the 999th element, which is really some random part of program memory. So, programmers who fet to perform this check open up their system to deliberate or accidental buffer overflow attacks. Servlets suffer from neither of these problems. Even if a servlet executes a system call (., with or JNI) to invoke a program on the local operating system, it does not use a shell to do so. And, of course, array bounds checking and other memory protection features are a central part of the Java programming language. 7． Mainstream There are a lot of good technologies out there. But if vendors don39。t support them and developers don39。t know how to use them, what good are they? Servlet and JSP technology is supported by servers from Apache, Oracle, IBM, Sybase, BEA, 東南大學成賢學院 畢業(yè)設計外文翻譯 [劉振雷 ]網上 購物系統(tǒng)設計與實現 11 Macromedia, Caucho, Sun/iPla, New Atlanta, ATG, Fujitsu, Lutris, Silverstream, the World Wide Web Consortium (W3C), and many others. Several lowcost plugins add support to Microsoft IIS and Zeus as well. They run on Windows, Unix/Linux, MacOS, VMS, and IBM mainframe operating systems. They are the single most popular application of the Java programming language. They are arguably the most popular choice for developing medium to large Web applications. They are used by the airline industry (most United Airlines and Delta Airlines Web sites), emerce (), online banking (First USA Bank, Banco Popular de Puerto Rico), Web search engines/portals (), large financial sites (American Century Investments), and hundreds of other sites that you visit every day. Of course, popularity alone is no proof of good technology. Numerous counterexamples abound. But our point is that you are not experimenting with a new and unproven technology when you work with serverside Java.