没有合适的资源?快使用搜索试试~ 我知道了~
外文文献及翻译-Java-and-the-Internet.doc
1 下载量 102 浏览量
2023-07-02
14:06:13
上传
评论
收藏 106KB DOC 举报
温馨提示
试读
19页
外文文献及翻译-Java-and-the-Internet.doc
资源推荐
资源详情
资源评论
1
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
2
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
3
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
4
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.)
4.Java
If a scripting language can solve 80 percent of the client-side programming
problems, what about the other 20 percent—the “really hard stuff?” The most
popular solution today is Java. Not only is it a powerful programming language
built to be secure, cross-platform, and international, but Java is being
continually extended to provide language features and libraries that elegantly
handle problems that are difficult in traditional programming languages, such as
multithreading, database access, network programming, and distributed
computing. Java allows client-side programming via the applet.
An applet is a mini-program that will run only under a Web browser. The
applet is downloaded automatically as part of a Web page (just as, for example,
a graphic is automatically downloaded). When the applet is activated it executes
a program. This is part of its beauty—it provides you with a way to
automatically distribute the client software from the server at the time the user
needs the client software, and no sooner. The user gets the latest version of the
client software without fail and without difficult reinstallation. Because of the
way Java is designed, the programmer needs to create only a single program,
and that program automatically works with all computers that have browsers
with built-in Java interpreters. (This safely includes the vast majority of
machines.) Since Java is a full-fledged programming language, you can do as
much work as possible on the client before and after making requests of the
剩余18页未读,继续阅读
资源评论
xinkai1688
- 粉丝: 349
- 资源: 8万+
上传资源 快速赚钱
- 我的内容管理 展开
- 我的资源 快来上传第一个资源
- 我的收益 登录查看自己的收益
- 我的积分 登录查看自己的积分
- 我的C币 登录后查看C币余额
- 我的收藏
- 我的下载
- 下载帮助
最新资源
- Servlet和JDBC实现三层架构
- Appium-Inspector-2024.6.1-win
- Screenshot_2024-06-14-21-22-39-202_net.csdn.csdnplus.jpg
- Appium-Server-GUI-windows-1.22.3-4
- 基于C语言+python实现的永磁同步电机矢量控制算法仿真+源码(毕业设计&课程设计&项目开发)
- APKPure_v3.20.05_apkpure.com.apk
- HKJC_AOSBS_PROD_L2.7R2Q_Build8172.apk
- jetson官网下载的官方资料
- 小游戏的java程序开发
- matlab GUI仿真资源.zip
资源上传下载、课程学习等过程中有任何疑问或建议,欢迎提出宝贵意见哦~我们会及时处理!
点击此处反馈
安全验证
文档复制为VIP权益,开通VIP直接复制
信息提交成功