JAVA外文文献翻译.doc_有关java的外文文献资源-CSDN文库

版权申诉

5星 · 超过95%的资源 126 浏览量 2022-06-10 00:07:35 上传评论收藏 62KB DOC 举报

Java 和互联网：编程革命 Java 被视为计算机编程领域的一次革命性步骤，原因在于它不仅是一个传统的编程语言，更是在解决全球万维网（World Wide Web）上的编程问题时发挥着重要作用。如果你是从传统编程的角度来看待 Java，它的独特之处可能并不明显。Java 的重要性体现在它为互联网带来了新的交互体验，尤其是在客户端编程方面。 1. 客户端编程互联网最初的设计是基于服务器-浏览器模式，这种模式下的交互完全由服务器提供。服务器生成静态页面供客户端浏览器解释并显示。基本的 HTML 提供了一些简单的数据收集机制，如文本输入框、复选框、单选按钮、列表和下拉列表，以及一个只能重置表单数据或“提交”表单数据回服务器的按钮。这个提交过程通过所有 Web 服务器都提供的通用网关接口（CGI）进行。提交的文本告诉 CGI 如何处理这些数据。最常见的动作是运行位于服务器上通常称为 "cgi-bin" 目录中的程序。当你在网页上点击按钮时，观察浏览器顶部的地址栏，有时你会看到 "cgi-bin" 在其中。这些程序可以用大多数语言编写，Perl 是常见选择之一，因为它专为文本操作设计，并且是解释型语言，可以在任何服务器上安装，不论处理器还是操作系统。许多强大的网站如今完全依赖 CGI 构建，实际上几乎可以做任何事情。然而，基于 CGI 程序构建的网站维护起来可能会变得过于复杂，而且响应时间也是一个问题。CGI 程序的响应速度取决于必须发送的数据量以及服务器和客户端的负载。 2. Java 的革新 Java 的出现改变了这一局面。它引入了“一次编写，到处运行”（Write Once, Run Anywhere，WORA）的概念，使得开发者能够在任何支持 Java 的平台上运行代码，而无需考虑底层硬件或操作系统。这极大地简化了开发和维护跨平台应用程序的过程。Java applet 是早期用于客户端的 Java 程序，它们可以直接在用户的浏览器中运行，提供动态和交互性的内容，而不再完全依赖服务器。这减轻了服务器的压力，提高了响应速度，同时也使用户能够享受更加丰富的在线体验。 3. Java Servlets 和 JSP 随着技术的发展，Java 进一步推出了 Java Servlets 和 JavaServer Pages（JSP）。Servlets 是服务器端的 Java 程序，它们扩展了 Web 服务器的功能，处理 HTTP 请求并生成动态内容。JSP 则将视图和逻辑分离，使得网页设计人员和程序员可以更有效地协作，提高了开发效率和代码的可维护性。 4. Java 与分布式计算 Java 还支持分布式计算，允许在多个网络连接的计算机之间高效地共享资源。例如，Java RMI（远程方法调用）和 EJB（企业级 JavaBean）让开发者能够创建分布式应用程序，实现跨越不同系统的组件通信。总结起来，Java 在互联网领域的革命性影响主要体现在以下几个方面： 1. 客户端编程能力的提升，通过 applets 实现了浏览器内的动态交互。 2. 通过 Java Servlets 和 JSP 改善了服务器端动态内容的生成，提供了更高效、可维护的开发模型。 3. 促进了分布式计算，使得跨系统通信成为可能。 4. 具有跨平台兼容性，降低了开发和维护成本。 Java 的这些特性使其在互联网时代扮演了不可或缺的角色，为开发者提供了强大而灵活的工具，推动了互联网应用的创新和发展。

资源推荐

资源详情

资源评论

Java and the Internet

If Java is, in fact, yet another computer programming language, you may

question why it is so important and why it is being promoted as a revolutionary

step in computer programming. The answer isn’t immediately obvious if you’re

coming from a traditional programming perspective. Although Java is very

useful for solving traditional stand-alone programming problems, it is also

important because it will solve programming problems on the World Wide Web.

1. Client-side programming

The Web’s initial server-browser design provided for interactive content, but

the interactivity was completely provided by the server. The server produced

static pages for the client browser, which would simply interpret and display

them. Basic HTML contains simple mechanisms for data gathering: text-entry

boxes, check boxes, radio boxes, lists and drop-down lists, as well as a button

that can only be programmed to reset the data on the form or “submit” the data

on the form back to the server. This submission passes through the Common

Gateway Interface (CGI) provided on all Web servers. The text within the

submission tells CGI what to do with it. The most common action is to run a

program located on the server in a directory that’s typically called “cgi-bin.” (If

you watch the address window at the top of your browser when you push a

button on a Web page, you can sometimes see “cgi-bin” within all the

gobbledygook there.) These programs can be written in most languages. Perl is a

common choice because it is designed for text manipulation and is interpreted,

so it can be installed on any server regardless of processor or operating system.

Many powerful Web sites today are built strictly on CGI, and you can in fact

do nearly anything with it. However, Web sites built on CGI programs can

rapidly become overly complicated to maintain, and there is also the problem of

response time. The response of a CGI program depends on how much data must

be sent, as well as the load on both the server and the Internet. (On top of this,

starting a CGI program tends to be slow.) The initial designers of the Web did

not foresee how rapidly this bandwidth would be exhausted for the kinds of

applications people developed. For example, any sort of dynamic graphing is

nearly impossible to perform with consistency because a GIF file must be

created and moved from the server to the client for each version of the graph.

And you’ve no doubt had direct experience with something as simple as

validating the data on an input form. You press the submit button on a page; the

data is shipped back to the server; the server starts a CGI program that discovers

an error, formats an HTML page informing you of the error, and then sends the

page back to you; you must then back up a page and try again. Not only is this

slow, it’s inelegant.

The solution is client-side programming. Most machines that run Web

browsers are powerful engines capable of doing vast work, and with the original

static HTML approach they are sitting there, just idly waiting for the server to

dish up the next page. Client-side programming means that the Web browser is

harnessed to do whatever work it can, and the result for the user is a much

speedier and more interactive experience at your Web site.

The problem with discussions of client-side programming is that they aren’t

very different from discussions of programming in general. The parameters are

almost the same, but the platform is different: a Web browser is like a limited

operating system. In the end, you must still program, and this accounts for the

dizzying array of problems and solutions produced by client-side programming.

The rest of this section provides an overview of the issues and approaches in

client-side programming.

2.Plug-ins

One of the most significant steps forward in client-side programming is the

development of the plug-in. This is a way for a programmer to add new

functionality to the browser by downloading a piece of code that plugs itself into

the appropriate spot in the browser. It tells the browser “from now on you can

perform this new activity.” (You need to download the plug-in only once.) Some

fast and powerful behavior is added to browsers via plug-ins, but writing a plug-

in is not a trivial task, and isn’t something you’d want to do as part of the

process of building a particular site. The value of the plug-in for client-side

programming is that it allows an expert programmer to develop a new language

and add that language to a browser without the permission of the browser

manufacturer. Thus, plug-ins provide a “back door” that allows the creation of

new client-side programming languages (although not all languages are

implemented as plug-ins).

3.Scripting languages

Plug-ins resulted in an explosion of scripting languages. With a scripting

language you embed the source code for your client-side program directly into

the HTML page, and the plug-in that interprets that language is automatically

activated while the HTML page is being displayed. Scripting languages tend to

be reasonably easy to understand and, because they are simply text that is part of

an HTML page, they load very quickly as part of the single server hit required to

procure that page. The trade-off is that your code is exposed for everyone to see

(and steal). Generally, however, you aren’t doing amazingly sophisticated things

with scripting languages so this is not too much of a hardship.

This points out that the scripting languages used inside Web browsers are

really intended to solve specific types of problems, primarily the creation of

richer and more interactive graphical user interfaces (GUIs). However, a

scripting language might solve 80 percent of the problems encountered in client-

side programming. Your problems might very well fit completely within that 80

percent, and since scripting languages can allow easier and faster development,

you should probably consider a scripting language before looking at a more

involved solution such as Java or ActiveX programming.

The most commonly discussed browser scripting languages are JavaScript

(which has nothing to do with Java; it’s named that way just to grab some of

Java’s marketing momentum), VBScript (which looks like Visual Basic), and

Tcl/Tk, which comes from the popular cross-platform GUI-building language.

There are others out there, and no doubt more in development.

JavaScript is probably the most commonly supported. It comes built into both

Netscape Navigator and the Microsoft Internet Explorer (IE). In addition, there

are probably more JavaScript books available than there are for the other

browser languages, and some tools automatically create pages using JavaScript.

However, if you’re already fluent in Visual Basic or Tcl/Tk, you’ll be more

productive using those scripting languages rather than learning a new one.

(You’ll have your hands full dealing with the Web issues already.)

剩余15页未读，继续阅读

评论收藏

内容反馈

版权申诉

limua123

2024-03-19

发现一个宝藏资源，赶紧冲冲冲！支持大佬~

omyligaga

粉丝: 97
资源: 2万+

JAVA外文文献翻译.doc

JAVA外文文献翻译

JAVA外文文献+翻译.doc

java毕业论文外文文献翻译.doc

J2ME和Java领域毕业设计外文文献翻译.doc

JAVA的学习-毕业设计外文文献翻译.doc

Java语言的发展-毕业设计外文文献翻译.doc

软件工程本科毕业外文文献翻译.doc

外文文献翻译

外文文献及翻译

J2ME和Java领域外文文献翻译.doc

Java IO 系统外文文献翻译.doc

java外文文献.doc

Android外文文献翻译.doc

JAVA外文文献毕业设计.doc

数据结构-外文翻译-外文文献-英文文献.doc

java图形化用户界面毕业设计的外文英文文献翻译.doc

java游戏类毕业设计外文文献翻译.doc

基于java的师资管理系统外文文献翻译.doc

网站建设外文文献翻译.doc

基于Java的教师管理系统外文文献翻译.doc

(完整word版)JAVA外文文献+翻译.doc

java基于struts+Hibernate的物流车辆调度系统外文文献翻译.doc

jsp动态网站技术--外文文献翻译.doc

Spring相关的外文文献翻译.zip

最新资源