jsp的技术发展历史

外文原文

The technique development history of JSP

The JSP(Java Server Pages) is from the company of Sun Microsystems initiate

，

the many companies the participate to the build up the together of the a kind the of

dynamic the state web the page technique standard, the it have the it in the construction

the of the dynamic state the web page the strong but the do not the especially of the

function. JSP and the technique of ASP of the Microsoft is very alike. Both all provide

the ability that mixes with a certain procedure code and is explain by the language

engine to carry out the procedure code in the code of HTML. Underneath we are simple

of carry on the introduction to it.

JSP pages arc translated into servlets. So, fundamentally, any task JSP pages can

perform could also be accomplished by servlets. However

，

this underlying equivalence

does not mean that servlets and JSP pages are equally appropriate in all scenarios. The

issue is not the power of the technology

，

it is the convenience

，

productivity

，

and

maintainability of one or the other. After all

，

anything you can do on a particular

computer platform in the Java programming language you could also do in assembly

language. But it still matters which you choose.

JSP provides the following benefits over servlets alone:

It is easier to write and maintain the HTML. Your static code is ordinary HTML:

no extra backslashes

，

no double quotes

，

and no lurking Java syntax.

You can use standard Web-site development tools. Even HTML tools that know

nothing about JSP can be used because they simply ignore the JSP tags.

You can divide up your development team. The Java programmers can work on the

dynamic code. The Web developers can concentrate on the presentation layer. On large

projects, this division is very important. Depending on the size of your team and the

complexity of your project

，

you can enforce a weaker or stronger separation between

the static HTML and the dynamic content.

Now

，

this discussion is not to say that you should stop using servlets and use only

JSP instead. By no means. Almost all projects will use both. For some requests in your

project

，

you will use servlets. For others

，

you will use JSP. For still others

，

you will

combine them with the MVC architecture . You want the appropriate tool for the job

，

and servlets

，

by themselves

，

do not complete your toolkit.

1.1 SOURCE OF JSP

The technique of JSP of the company of Sun

，

making the page of Web develop

the personnel can use the HTML perhaps marking of XML to design to turn the end

page with format. Use the perhaps small script future life of marking of JSP becomes the

dynamic state on the page contents.(the contents changes according to the claim

of)

The Java Servlet is a technical foundation of JSP

，

and the large Web applies the

development of the procedure to need the Java Servlet to match with with the JSP and

then can complete

，

this name of Servlet comes from the Applet

，

the local translation

method of now is a lot of

，

this book in order not to misconstruction, decide the direct

adoption Servlet but don’t do any translation, if reader would like to, can call it as’’

small service procedure”. The Servlet is similar to traditional CGI

，

ISAPI

，

NSAPI etc.

Web procedure development the function of the tool in fact, at use the Java Servlet

hereafter, the customer need not use again the lowly method of CGI of efficiency, also

need not use only the ability come to born page of Web of dynamic state in the method

of API that a certain fixed Web server terrace circulate. Many servers of Web all support

the Servlet

，

even not support the Servlet server of Web directly and can also pass the

additional applied server and the mold pieces to support the Servlet. Receive benefit in

the characteristic of the Java cross-platform, the Servlet is also a terrace irrelevant

，

actually

，

as long as match the norm of Java Servlet

，

the Servlet is complete to have

nothing to do with terrace and is to have nothing to do with server of Web. Because the

Java Servlet is internal to provide the service by the line distance, need not start a

progress to the each claimses

，

and make use of the multi-threading mechanism can at

the same time for several claim service, therefore the efficiency of Java Servlet is very

high.

But the Java Servlet also is not to has no weakness

，

similar to traditional CGI

，

ISAPI, the NSAPI method, the Java Servlet is to make use of to output the HTML

language sentence to carry out the dynamic state web page of

，

if develop the whole

website with the Java Servlet

，

the integration process of the dynamic state part and the

static state page is an evil-foreboding dream simply. For solving this kind of weakness

of the Java Servlet, the SUN released the JSP.

A number of years ago, Marty was invited to attend a small 20-pcrson industry

roundtable discussion on software technology. Sitting in the seat next to Marty was

James Gosling, inventor of the Java programming language. Sitting several scats away

was a high-level manager from a very large software company in Redmond

，

Washington. During the discussion, the moderator brought up the subject of Jini

，

which at that time was a new Java technology. The moderator asked the manager what

he thought of it

，

and the manager responded that it was too early to tell

，

but that it

seemed to be an excellent idea. He went on to say that they would keep an eye on it

，

and if it seemed to be catching on

，

they would follow his company’s usual cmbracc

and extend” strategy. At this point

，

Gosling lightheartedly interjected "You mean

n