英语文献翻译网上商城JAVA.docx

1、英语文献翻译网上商城JAVA毕业设计（论文）外文翻译题目：基于Java的网上商城系统的设计与实现 院 （系）： 计算机科学与工程 专 业： 网络工程 班 级： 070607 学 生： 冯 宁 学 号： * * * * 2011年 05 月09日English OnlyJava and the InternetIf 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 revolut

2、ionary step in computer programming. The answer isnt immediately obvious if youre coming from a traditional programming perspective. Although Java is very useful for solving traditional standalone programming problems, it is also important because it will solve programming problems on the World Wide

3、 Web. What is the Web?The Web can seem a bit of a mystery at first, with all this talk of “surfing,” “presence,” and “home pages.” Its helpful to step back and see what it really is, but to do this you must understand client/server systems, another aspect of computing thats full of confusing issues.

4、 1.Client/Server computingThe primary idea of a client/server system is that you have a central repository of informationsome kind of data, often in a databasethat you want to distribute on demand to some set of people or machines. A key to the client/server concept is that the repository of informa

5、tion is centrally located so that it can be changed and so that those changes will propagate out to the information consumers. Taken together, the information repository, the software that distributes the information, and the machine(s) where the information and software reside is called the server.

6、 The software that resides on the remote machine, communicates with the server, fetches the information, processes it, and then displays it on the remote machine is called the client.The basic concept of client/server computing, then, is not so complicated. The problems arise because you have a sing

7、le server trying to serve many clients at once. Generally, a database management system is involved, so the designer “balances” the layout of data into tables for optimal use. In addition, systems often allow a client to insert new information into a server. This means you must ensure that one clien

8、ts new data doesnt walk over another clients new data, or that data isnt lost in the process of adding it to the database (this is called transaction processing). As client software changes, it must be built, debugged, and installed on the client machines, which turns out to be more complicated and

9、expensive than you might think. Its especially problematic to support multiple types of computers and operating systems. Finally, theres the all-important performance issue: You might have hundreds of clients making requests of your server at any one time, so any small delay is crucial. To minimize

10、latency, programmers work hard to offload processing tasks, often to the client machine, but sometimes to other machines at the server site, using so-called middleware. (Middleware is also used to improve maintainability.) The simple idea of distributing information has so many layers of complexity

11、that the whole problem can seem hopelessly enigmatic. And yet its crucial: Client/server computing accounts for roughly half of all programming activities. Its responsible for everything from taking orders and credit-card transactions to the distribution of any kind of datastock market, scientific,

12、government, you name it. What weve come up with in the past is individual solutions to individual problems, inventing a new solution each time. These were hard to create and hard to use, and the user had to learn a new interface for each one. The entire client/server problem needs to be solved in a

13、big way. 2.The Web as a giant serverThe Web is actually one giant client/server system. Its a bit worse than that, since you have all the servers and clients coexisting on a single network at once. You dont need to know that, because all you care about is connecting to and interacting with one serve

14、r at a time (even though you might be hopping around the world in your search for the correct server). Initially it was a simple one-way process. You made a request of a server and it handed you a file, which your machines browser software (i.e., the client) would interpret by formatting onto your l

15、ocal machine. But in short order people began wanting to do more than just deliver pages from a server. They wanted full client/server capability so that the client could feed information back to the server, for example, to do database lookups on the server, to add new information to the server, or

16、to place an order (which required more security than the original systems offered). These are the changes weve been seeing in the development of the Web. The Web browser was a big step forward: the concept that one piece of information could be displayed on any type of computer without change. Howev

17、er, browsers were still rather primitive and rapidly bogged down by the demands placed on them. They werent particularly interactive, and tended to clog up both the server and the Internet because any time you needed to do something that required programming you had to send information back to the s

18、erver to be processed. It could take many seconds or minutes to find out you had misspelled something in your request. Since the browser was just a viewer it couldnt perform even the simplest computing tasks. (On the other hand, it was safe, because it couldnt execute any programs on your local mach

19、ine that might contain bugs or viruses.) To solve this problem, different approaches have been taken. To begin with, graphics standards have been enhanced to allow better animation and video within browsers. The remainder of the problem can be solved only by incorporating the ability to run programs

20、 on the client end, under the browser. This is called client-side programming. Client-side programmingThe Webs 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 w

21、ould simply interpret and display them. Basic HyperText Markup Language (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 t

22、he 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 thats typically called “cgi-bin.” (I

23、f 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 has been a common choice because it is designed for text manipulation and is inter

24、preted, so it can be installed on any server regardless of processor or operating system. However, Python (my favoritesee www.Python.org) has been making inroads because of its greater power and simplicity. Many powerful Web sites today are built strictly on CGI, and you can in fact do nearly anythi

25、ng with CGI. 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, star

26、ting 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 Graphics Interchan

27、ge Format (GIF) file must be created and moved from the server to the client for each version of the graph. And youve 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 se

28、rver 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, its inelegant. The solution is client-side programming. Most machines that run Web browsers are

29、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

30、 speedier and more interactive experience at your Web site. The problem with discussions of client-side programming is that they arent 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 operati

31、ng 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. 1.Plug-insOne of the most significant steps fo

32、rward 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 isnt something youd want to do as part of the process of building a particular site. The value of the plug-in fo