【正文】 ient/server approaches you have the problem of multiple types of client puters, as well as the difficulty of installing new client software, both of which are handily solved with Web browsers and clientside programming. When Web technology is used for an information work that is restricted to a particular pany, it is referred to as an intra. Intras provide much greater security than the Inter, since you can physically control access to the servers within your pany. In terms of training, it seems that once people understand the general concept of a browser it’s much easier for them to deal with differences in the way pages and applets look, so the learning curve for new kinds of systems seems to be reduced. The security problem brings us to one of the divisions that seems to be automatically forming in the world of clientside programming. If your program is running on the Inter, you don’t know what platform it will be working under, and you want to be extra careful that you don’t disseminate buggy code. You need something crossplatform and secure, like a scripting language or Java. If you’re running on an intra, you might have a different set of constraints. It’s not unmon that your machines could all be Intel/Windows platforms. On an intra, you’re responsible for the quality of your own code and can repair bugs when they’re discovered. In addition, you might already have a body of legacy code that you’ve been using in a more traditional client/server approach, whereby you must physically install client programs every time you do an upgrade. The time wasted in installing upgrades is the most pelling reason to move to browsers, because upgrades are invisible and automatic. If you are involved in such an intra, the most sensible approach to take is the shortest path that allows you to use your existing code base, rather than trying to recode your programs in a new language. When faced with this bewildering array of solutions to the clientside programming problem, the best plan of attack is a costbenefit analysis. Consider the constraints of your problem and what would be the shortest path to your solution. Since clientside programming is still programming, it’s always a good idea to take the fastest development approach for your particular situation. This is an aggressive stance to prepare for inevitable encounters with the problems of program development. 翻譯： Java和因特網(wǎng) Java 除了可解決傳統(tǒng)的程序設(shè)計問題以外，還能解決 World Wide Web(萬維網(wǎng) )上的編程問題。 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。 西安郵電 大學 畢 業(yè) 設(shè) 計（論 文） 外文文獻翻譯 院 （系） ： 計算機 學院 專 業(yè)： 計算機科學與技術(shù) 班 級： 學生姓名： 導師姓名： 職稱： 起止時間： 2021 年 9月 23日 至 2021年 6月 2日 原文 ： Java and the Inter 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 Web. 1. Clientside programming The Web’s initial serverbrowser design provided for interactive content, but the interactivity was pletely 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: textentry boxes, check boxes, radio boxes, lists and dropdown lists, as well as a b