




版權(quán)說明:本文檔由用戶提供并上傳,收益歸屬內(nèi)容提供方,若內(nèi)容存在侵權(quán),請進(jìn)行舉報或認(rèn)領(lǐng)
文檔簡介
1、.Servlet和JSP技術(shù)簡介中英文資料外文翻譯文獻(xiàn)An Overview of Servlet and JSP TechnologyMarty Hall and Larry Brown,2000-07, Core Servlets and JavaServer Pages chapter 11.1 A Servlet's JobServlets are Java programs that run on Web or application servers, acting as a middle layer between requests coming from Web brow
2、sers or other HTTP clients and databases or applications on the HTTP server. Their job is to perform the following tasks, as illustrated in Figure 1-1.Figure 1-11Read the explicit data sent by the client.The end user normally enters this data in an HTML form on a Web page. However, the data could al
3、so come from an applet or a custom HTTP client program.2Read the implicit HTTP request data sent by the browser.Figure 1-1 shows a single arrow going from the client to the Web server (the layer where servlets and JSP execute), but there are really two varieties of data: the explicit data that the e
4、nd user enters in a form and the behind-the-scenes HTTP information. Both varieties are critical. The HTTP information includes cookies, information about media types and compression schemes the browser understands, and so on.3Generate the results.This process may require talking to a database, exec
5、uting an RMI or EJB call, invoking a Web service, or computing the response directly. Your real data may be in a relational database. Fine. But your database probably doesn't speak HTTP or return results in HTML, so the Web browser can't talk directly to the database. Even if it could, for s
6、ecurity reasons, you probably would not want it to. The same argument applies to most other applications. You need the Web middle layer to extract the results inside a document.4Send the explicit data (i.e., the document) to the client.This document can be sent in a variety of formats, including tex
7、t (HTML or XML), binary (GIF images), or even a compressed format like gzip that is layered on top of some other underlying format. But, HTML is by far the most common format, so an important servlet/JSP task is to wrap the results inside of HTML.5Send the implicit HTTP response data.Figure 1-1 show
8、s a single arrow going from the Web middle layer (the servlet or JSP page) to the client. But, there are really two varieties of data sent: the document itself and the behind-the-scenes HTTP information. Again, both varieties are critical to effective development. Sending HTTP response data involves
9、 telling the browser or other client what type of document is being returned (e.g., HTML), setting cookies and caching parameters, and other such tasks. 1.2 Why Build Web Pages Dynamically?Many client requests can be satisfied by prebuilt documents, and the server would handle these requests without
10、 invoking servlets. In many cases, however, a static result is not sufficient, and a page needs to be generated for each request. There are a number of reasons why Web pages need to be built on-the-fly:1 The Web page is based on data sent by the client.For instance, the results page from search engi
11、nes and order-confirmation pages at online stores are specific to particular user requests. You don't know what to display until you read the data that the user submits. Just remember that the user submits two kinds of data: explicit (i.e., HTML form data) and implicit (i.e., HTTP request header
12、s). Either kind of input can be used to build the output page. In particular, it is quite common to build a user-specific page based on a cookie value.2The Web page is derived from data that changes frequently.If the page changes for every request, then you certainly need to build the response at re
13、quest time. If it changes only periodically, however, you could do it two ways: you could periodically build a new Web page on the server (independently of client requests), or you could wait and only build the page when the user requests it. The right approach depends on the situation, but sometime
14、s it is more convenient to do the latter: wait for the user request. For example, a weather report or news headlines site might build the pages dynamically, perhaps returning a previously built page if that page is still up to date.3The Web page uses information from corporate databases or other ser
15、ver-side sources.If the information is in a database, you need server-side processing even if the client is using dynamic Web content such as an applet. Imagine using an applet by itself for a search engine site:"Downloading 50 terabyte applet, please wait!" Obviously, that is silly; you n
16、eed to talk to the database. Going from the client to the Web tier to the database (a three-tier approach) instead of from an applet directly to a database (a two-tier approach) provides increased flexibility and security with little or no performance penalty. After all, the database call is usually
17、 the rate-limiting step, so going through the Web server does not slow things down. In fact, a three-tier approach is often faster because the middle tier can perform caching and connection pooling.In principle, servlets are not restricted to Web or application servers that handle HTTP requests but
18、can be used for other types of servers as well. For example, servlets could be embedded in FTP or mail servers to extend their functionality. And, a servlet API for SIP (Session Initiation Protocol) servers was recently standardized (see /en/jsr/detail?id=116). In practice, however, thi
19、s use of servlets has not caught on, and we'll only be discussing HTTP servlets.1.3 The Advantages of Servlets Over "Traditional" CGIJava servlets are more efficient, easier to use, more powerful, more portable, safer, and cheaper than traditional CGI and many alternative CGI-like tech
20、nologies.1EfficientWith traditional CGI, a new process is started for each HTTP request. If the CGI program itself is relatively short, the overhead of starting the process can dominate the execution time. With servlets, the Java virtual machine stays running and handles each request with a lightwei
21、ght Java thread, not a heavyweight operating system process. Similarly, in traditional CGI, if there are N requests to the same CGI program, the code for the CGI program is loaded into memory N times. With servlets, however, there would be N threads, but only a single copy of the servlet class would
22、 be loaded. This approach reduces server memory requirements and saves time by instantiating fewer objects. Finally, when a CGI program finishes handling a request, the program terminates. This approach makes it difficult to cache computations, keep database connections open, and perform other optim
23、izations that rely on persistent data. Servlets, however, remain in memory even after they complete a response, so it is straightforward to store arbitrarily complex data between client requests.2ConvenientServlets have an extensive infrastructure for automatically parsing and decoding HTML form dat
24、a, reading and setting HTTP headers, handling cookies, tracking sessions, and many other such high-level utilities. In CGI, you have to do much of this yourself. Besides, if you already know the Java programming language, why learn Perl too? You're already convinced that Java technology makes fo
25、r more reliable and reusable code than does Visual Basic, VBScript, or C+. Why go back to those languages for server-side programming?3PowerfulServlets support several capabilities that are difficult or impossible to accomplish with regular CGI. Servlets can talk directly to the Web server, whereas
26、regular CGI programs cannot, at least not without using a server-specific API. Communicating with the Web server makes it easier to translate relative URLs into concrete path names, for instance. Multiple servlets can also share data, making it easy to implement database connection pooling and simil
27、ar resource-sharing optimizations. Servlets can also maintain information from request to request, simplifying techniques like session tracking and caching of previous computations.4PortableServlets are written in the Java programming language and follow a standard API. Servlets are supported direct
28、ly or by a plugin on virtually every major Web server. Consequently, servlets written for, say, Macromedia JRun can run virtually unchanged on Apache Tomcat, Microsoft Internet Information Server (with a separate plugin), IBM WebSphere, iPlanet Enterprise Server, Oracle9i AS, or StarNine WebStar. Th
29、ey are part of the Java 2 Platform, Enterprise Edition (J2EE; see so industry support for servlets is becoming even more pervasive.5InexpensiveA number of free or very inexpensive Web servers are good for development use or deployment of low- or medium-volume Web sites. Thus, with servlets and JSP y
30、ou can start with a free or inexpensive server and migrate to more expensive servers with high-performance capabilities or advanced administration utilities only after your project meets initial success. This is in contrast to many of the other CGI alternatives, which require a significant initial i
31、nvestment for the purchase of a proprietary package.Price and portability are somewhat connected. For example, Marty tries to keep track of the countries of readers that send him questions by email. India was near the top of the list, probably #2 behind the U.S. Marty also taught one of his JSP and
32、servlet training courses (see in Manila, and there was great interest in servlet and JSP technology there.Now, why are India and the Philippines both so interested? We surmise that the answer is twofold. First, both countries have large pools of well-educated software developers. Second, both countr
33、ies have (or had, at that time) highly unfavorable currency exchange rates against the U.S. dollar. So, buying a special-purpose Web server from a U.S. company consumed a large part of early project funds.But, with servlets and JSP, they could start with a free server: Apache Tomcat (either standalo
34、ne, embedded in the regular Apache Web server, or embedded in Microsoft IIS). Once the project starts to become 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 rew
35、ritten. If their project becomes 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 pr
36、oject becomes quite large and complex, 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 becomes even bigger, they mig
37、ht 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.6SecureOne of the main sources of vulnerabilities in traditional CGI stems from the fact that the programs are often executed by general-purpose
38、 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 i
39、n 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 100-element array and then write into the 999th "element,&qu
40、ot; which is really some random part of program memory. So, programmers who forget 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 (e.g., with Runtime.exec or JNI)
41、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.7MainstreamThere are a lot of good technologies out there. But if vendors don't supp
42、ort them and developers don't know how to use them, what good are they? Servlet and JSP technology is supported by servers from Apache, Oracle, IBM, Sybase, BEA, Macromedia, Caucho, Sun/iPlanet, New Atlanta, ATG, Fujitsu, Lutris, Silverstream, the World Wide Web Consortium (W3C), and many others
43、. Several low-cost 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 t
44、o large Web applications. They are used by the airline industry (most United Airlines and Delta Airlines Web sites), e-commerce (), online banking (First USA Bank, Banco Popular de Puerto Rico), Web search engines/portals (), large financial sites (American Century Investments), and hundreds of othe
45、r sites that you visit every day.Of course, popularity alone is no proof of good technology. Numerous counter-examples abound. But our point is that you are not experimenting with a new and unproven technology when you work with server-side Java.摘要:Servlet 程序運(yùn)行在服務(wù)器端,在動態(tài)的生成Web頁面方面與傳統(tǒng)的CGI和許多其他的類似CGI技術(shù)
46、相比,Java Servlet更高效,更容易使用,功能更強(qiáng)大,并且擁有更好的可移植性,更節(jié)省投資。關(guān)鍵詞:JSP 技術(shù),Servlet,HTTP服務(wù)Servlet和JSP技術(shù)簡介Marty Hall and Larry Brown,2000-07,chapter 11.1 Servlet的功能Servlets是運(yùn)行在Web或應(yīng)用服務(wù)器上的Java程序,它是一個中間層,負(fù)責(zé)連接來自Web瀏覽器或其他HTTP客戶端和HTTP服務(wù)器上的數(shù)據(jù)庫或應(yīng)用程序。Servlet的工作是執(zhí)行下面的任務(wù),如圖1-1所示 。圖1-11. 讀取客戶端發(fā)送的顯式數(shù)據(jù)??蛻舳擞脩粢话阍陧撁娴腍TML表單中輸入這些數(shù)據(jù)。然
47、而,數(shù)據(jù)還有可能來自applet或定制的HTTP客戶程序。2. 讀取由瀏覽器發(fā)送的隱式請求數(shù)據(jù)。圖1-1中顯示了一條從客戶端到Web服務(wù)器的單箭頭,但實(shí)際上從客戶端傳送到Web服務(wù)器的數(shù)據(jù)有兩種,它們分別為用戶在表單中輸入的顯式數(shù)據(jù),以及后臺的HTTP信息。兩種數(shù)據(jù)都很重要。HTTP信息包括cookie、瀏覽器所能識別的媒體類型和壓縮模式等。3. 生成結(jié)果。這個過程可能需要訪問數(shù)據(jù)庫、執(zhí)行RMI或EJB調(diào)用、調(diào)用Web服務(wù),或者直接計(jì)算得出對應(yīng)的響應(yīng)。實(shí)際的數(shù)據(jù)可能存儲在關(guān)系型數(shù)據(jù)庫中。但是該數(shù)據(jù)庫可能不理解HTTP,或者不能返回HTML形式的結(jié)果,所以Web瀏覽器不能直接與數(shù)據(jù)庫進(jìn)行會話。即
48、使它能夠做到這一點(diǎn),為了安全上的考慮,我們也不希望讓它這么做。對應(yīng)大多數(shù)其他應(yīng)用程序,也存在類似的問題。因此,我們需要Web中間層從HTTP流中提取輸入數(shù)據(jù),與應(yīng)用程序會話,并將結(jié)果嵌入到文檔中。4. 向客戶發(fā)送顯式數(shù)據(jù)(即文檔)。這個文檔可以用各種格式發(fā)送,包括文本(HTML或XML),二進(jìn)制(GIF圖像),甚至可以是建立在其他底層格式之上的壓縮格式,如gzip。但是,到目前為止,HTML式最常用的格式,故而Servlet/JSP的重要任務(wù)之一就是將結(jié)果包裝到HTML中。5. 發(fā)送隱式的HTTP響應(yīng)數(shù)據(jù)。圖1-1中顯示了一條從Web中間層到客戶端的單箭頭。但是,實(shí)際發(fā)送的數(shù)據(jù)有兩種:文檔本身
49、,以及后臺的HTTP信息。同樣,兩種數(shù)據(jù)對開發(fā)來說都是至關(guān)重要的。HTTP響應(yīng)數(shù)據(jù)的發(fā)送過程涉及告知瀏覽器或其他客戶程序所返回文檔的類型(如HTML),設(shè)置cookie和緩存參數(shù),以及其他類似的任務(wù)。1.2 動態(tài)構(gòu)建網(wǎng)頁的原因預(yù)先建立的文檔可以滿足客戶的許多請求,服務(wù)器無需調(diào)用servlet就可以處理這些請求。然而,許多情況下靜態(tài)的結(jié)果不能滿足要求,我們需要針對每個請求生成一個頁面。實(shí)時構(gòu)建頁面的理由有很多種:1、網(wǎng)頁基于客戶發(fā)送的數(shù)據(jù)。例如,搜索引擎生成的頁面,以及在線商店的訂單確認(rèn)頁面,都要針對特定的用戶請求而產(chǎn)生。在沒有讀取到用戶提交的數(shù)據(jù)之前,我們不知道應(yīng)該顯示什么。要記住,用戶提交兩
50、種類型的數(shù)據(jù):顯示(即HTML表單的數(shù)據(jù))和隱式(即HTTP請求的報頭)。兩種輸入都可用來構(gòu)建輸出頁面?;赾ookie值針對具體用戶構(gòu)建頁面的情況尤其普遍。2、頁面由頻繁改變的數(shù)據(jù)導(dǎo)出。如果頁面需要根據(jù)每個具體的請求做出相應(yīng)的改變,當(dāng)然需要在請求發(fā)生時構(gòu)建響應(yīng)。但是,如果頁面周期性地改變,我們可以用兩種方式來處理它:周期性地在服務(wù)器上構(gòu)建新的頁面(和客戶請求無關(guān)),或者僅僅在用戶請求該頁面時再構(gòu)建。具體應(yīng)該采用哪種方式要根據(jù)具體情況而定,但后一種方式常常更為方便,因?yàn)樗恍韬唵蔚氐却脩舻恼埱?。例如,天氣預(yù)報或新聞網(wǎng)站可能會動態(tài)地構(gòu)建頁面,也有可能會返回之前構(gòu)建的頁面(如果它還是最新的話)。
51、3、頁面中使用了來自公司數(shù)據(jù)庫或其他數(shù)據(jù)庫斷數(shù)據(jù)源的信息。如果數(shù)據(jù)存儲在數(shù)據(jù)庫中,那么,即使客戶端使用動態(tài)Web內(nèi)容,比如applet,我們依舊需要執(zhí)行服務(wù)器端處理。想象以下,如果一個搜索引擎網(wǎng)站完全使用applet,那么用戶將會看到:“正在下載50TB的applet,請等待!”。顯然,這樣很愚蠢;這種情況下,我們需要與數(shù)據(jù)庫進(jìn)行會話。從客戶端到Web層再到數(shù)據(jù)庫(三層結(jié)構(gòu)),要比從applet直接到數(shù)據(jù)庫(二層結(jié)構(gòu))更靈活,也更安全,而性能上的損失很少甚至沒有。畢竟數(shù)據(jù)庫調(diào)用通常是對速度影響最大的步驟,因而,經(jīng)過中間層可以執(zhí)行高速緩存和連接共享。理論上講,servlet并非只用于處理HTTP
52、請求的Web服務(wù)器或應(yīng)用服務(wù)器,它同樣可以用于其他類型的服務(wù)器。例如,servlet能夠嵌入到FTP或郵件服務(wù)器中,擴(kuò)展他們的功能。而且,用于會話啟動協(xié)議服務(wù)器的servlet API最近已經(jīng)被標(biāo)準(zhǔn)化(參見/en/jsr/detail?id=116)。但在實(shí)踐中,servlet的這種用法尚不流行,在此,我們只論述HTTP Servlet。1.3 Servlet相對于“傳統(tǒng)”CGI的優(yōu)點(diǎn)和傳統(tǒng)CGI及許多類CGI技術(shù)相比,Java servlet更高效、更易用、更強(qiáng)大、更容易移植、更安全、也更廉價。1、高效應(yīng)用傳統(tǒng)的CGI,針對每個HTTP請求都用啟動一個新的進(jìn)程。如果
53、CGI程序自身相對比較簡短,那么啟動進(jìn)程的開銷會占用大部分執(zhí)行時間。而使用servlet,Java虛擬機(jī)會一直運(yùn)行,并用輕量級的Java線程處理每個請求,而非重量級的操作系統(tǒng)進(jìn)程。類似地,應(yīng)用傳統(tǒng)的CGI技術(shù),如果存在對同一CGI程序的N個請求,那么CGI程序的代碼會載入內(nèi)存N次。同樣的情況,如果使用servlet,則啟動N個線程,但是僅僅載入servlet類的單一副本。這種方式減少了服務(wù)器的內(nèi)存需求,通過實(shí)例化更少的對象從而節(jié)省了時間。最后,當(dāng)CGI程序結(jié)束對請求的處理之后,程序結(jié)束。這種方式難以緩存計(jì)算結(jié)果,保持?jǐn)?shù)據(jù)庫連接打開,或是執(zhí)行依靠持續(xù)性數(shù)據(jù)的其他優(yōu)化。然而,servlet會一直停
54、留在內(nèi)存中(即使請求處理完畢),因而可以直接存儲客戶請求之間的任意復(fù)雜數(shù)據(jù)。2、便利Servlet提供大量的基礎(chǔ)構(gòu)造,可以自動分析和解碼HTML的表單數(shù)據(jù),讀取和設(shè)置HTTP報頭,處理cookie,跟蹤會話,以及其他此類高級功能。而在CGI中,大部分工作都需要我們資金完成。另外,如果您已經(jīng)了解了Java編程語言,為什么還有學(xué)校Perl呢?您已經(jīng)承認(rèn)應(yīng)用Java技術(shù)編寫的代碼要比Visual Basic,VBScript或C編寫的代碼更可靠,且更易重用,為什么還有倒退回去選擇那些語言來開發(fā)服務(wù)器端的程序呢?3、強(qiáng)大Servlet支持常規(guī)CGI難以實(shí)現(xiàn)或根本不能實(shí)現(xiàn)的幾項(xiàng)功能。Servlet能夠直接于Web服務(wù)器對話,而常規(guī)的CGI程序做不到這一點(diǎn),至少在不使用服務(wù)器專有API的情況下是這樣。例如,與Web服務(wù)器的通信使得講相對URL轉(zhuǎn)換成具體的路徑名變得更為容易。多個servlet還可以共享數(shù)據(jù),從而易于實(shí)現(xiàn)數(shù)據(jù)庫連接共享和類似的資源共享優(yōu)化。Servlet還能維護(hù)請求之間的信息,使得諸如會話跟蹤和計(jì)算結(jié)果緩存等技術(shù)變得更為簡單。4、可移植性Servlet使用Java編程語言,并且遵循標(biāo)準(zhǔn)的API。所有主要的Web服務(wù)器。實(shí)際上都
溫馨提示
- 1. 本站所有資源如無特殊說明,都需要本地電腦安裝OFFICE2007和PDF閱讀器。圖紙軟件為CAD,CAXA,PROE,UG,SolidWorks等.壓縮文件請下載最新的WinRAR軟件解壓。
- 2. 本站的文檔不包含任何第三方提供的附件圖紙等,如果需要附件,請聯(lián)系上傳者。文件的所有權(quán)益歸上傳用戶所有。
- 3. 本站RAR壓縮包中若帶圖紙,網(wǎng)頁內(nèi)容里面會有圖紙預(yù)覽,若沒有圖紙預(yù)覽就沒有圖紙。
- 4. 未經(jīng)權(quán)益所有人同意不得將文件中的內(nèi)容挪作商業(yè)或盈利用途。
- 5. 人人文庫網(wǎng)僅提供信息存儲空間,僅對用戶上傳內(nèi)容的表現(xiàn)方式做保護(hù)處理,對用戶上傳分享的文檔內(nèi)容本身不做任何修改或編輯,并不能對任何下載內(nèi)容負(fù)責(zé)。
- 6. 下載文件中如有侵權(quán)或不適當(dāng)內(nèi)容,請與我們聯(lián)系,我們立即糾正。
- 7. 本站不保證下載資源的準(zhǔn)確性、安全性和完整性, 同時也不承擔(dān)用戶因使用這些下載資源對自己和他人造成任何形式的傷害或損失。
最新文檔
- 上海市上戲附中2025屆高一下化學(xué)期末教學(xué)質(zhì)量檢測模擬試題含解析
- 農(nóng)機(jī)中心制度管理辦法
- 合肥建設(shè)行業(yè)管理辦法
- 殯葬服務(wù)租賃管理辦法
- 村級代管資金管理辦法
- 超高壓擠包直流電纜絕緣系統(tǒng)技術(shù)難點(diǎn)及解決方案研究
- 華為薪資待遇管理辦法
- 數(shù)據(jù)安全策略-第2篇-洞察及研究
- 腳手架施工方案:高空作業(yè)安全
- 廚房管理辦法實(shí)施細(xì)則
- 職工代表選舉方案及選票模版(2篇)
- 血透室護(hù)理安全管理及防范
- 廣東發(fā)布智慧公路標(biāo)準(zhǔn)體系(2024版)
- 電商直播平臺主播操作手冊
- ASTM-D3359-(附著力測試標(biāo)準(zhǔn))-中文版
- 石嘴山市直機(jī)關(guān)遴選公務(wù)員筆試真題2022
- 吉林省吉林市亞橋中學(xué)2023-2024學(xué)年七年級下學(xué)期期末考試數(shù)學(xué)試卷
- 貴州省貴陽市南明區(qū)2023-2024學(xué)年四年級下學(xué)期期末數(shù)學(xué)質(zhì)量監(jiān)測
- DL-T5706-2014火力發(fā)電工程施工組織設(shè)計(jì)導(dǎo)則
- 2024-2030年殷瓦鋼行業(yè)市場現(xiàn)狀供需分析及重點(diǎn)企業(yè)投資評估規(guī)劃分析研究報告
- 第一目擊者理論考試題題庫110題
評論
0/150
提交評論