java大学设备管理系统计算机毕业设计英文文献翻译

java大学设备管理系统计算机毕业设计英文文献翻译内容摘要：

aution is harder than one might think, and weaknesses stemming from this problem are constantly being uncovered in widely used CGI libraries. A second source of problems is the fact that some CGI programs are processed by languages that do not automatically check array or string bounds. For example, in C and C++ it is perfectly legal to allocate a 100element array and then write into the 999th element, which is really some random part of program memory. So, programmers who fet to perform this check open up their system to deliberate or accidental buffer overflow attacks. Servlets suffer from neither of these problems. Even if a servlet executes a system call (., with or JNI) to invoke a program on the local operating system, it does not use a shell to do so. And, of course, array bounds checking and other memory protection features are a central part of the Java programming language. 7． Mainstream There are a lot of good technologies out there. But if vendors don39。 t support them and developers don39。 t know how to use them, what good are they? Servlet and JSP technology is supported by servers from Apache, Oracle, IBM, Sybase, BEA, Macromedia, Caucho, Sun/iPla, New Atlanta, ATG, Fujitsu, Lutris, Silverstream, the World Wide Web Consortium (W3C), and many others. Several lowcost plugins add support to Microsoft IIS and Zeus as well. They run on Windows, Unix/Linux, MacOS, VMS, and IBM mainframe operating systems. They are the single most popular application of the Java programming language. They are arguably the most popular choice for developing medium to large Web applications. They are used by the airline industry (most United Airlines and Delta Airlines Web sites), emerce (), online banking (First USA Bank, Banco Popular de Puerto Rico), Web search engines/portals (), large financial sites (American Century Investments), and hundreds of other sites that you visit every day. Of course, popularity alone is no proof of good technology. Numerous counterexamples abound. But our point is that you are not experimenting with a new and unproven technology when you work with serverside Java. Before diving into an explanation of presentation technology, it39。 s helpful to fill in some details on the situation that led to the birth of the technology. Just 10 short years ago, the term thin client was a novelty. We still lived in a world of desktop applications, powered by wimpy 286 microprocessors with 14inch monitors that we squinted at. Boy, have times changed! Now my desktop does nothing but power a Web browser, while servers from Sun, IBM, HP, Compaq, and the rest churn out putations, business logic, and content. And that little monitor? Replaced by flatscreen, plasma, whopping 21 and 25inch beauties. Why? So we can see the intricate and plex HTML displays that serve as a frontend to these powerful applications. No longer does a clunky interface suffice。 now we expect flashy graphics, moving images, colorcoordinated presentations that would look good in any room in the house, and speedy rendering to premiseToday, a decade beyond those fledgling Windows applications, we are still dealing with this huge shift in the presentation paradigm. The woeful Visual Basic and C programmers who remain now find themselves working either on backend systems or Windowsonly applications, or they have added a Webcapable language such as the Java language to their toolbox. An application that doesn39。 t support at least three of four MLisms such as HTML, XML, and WML is considered shabby, if not an outright failure. And, of course, that means we all care very deeply about the ability to easily develop a Web presentation it turns out, using the new Inter, and all the languages we have at our disposal Java, C, Perl, Pascal, and Ada, among others hasn39。 t been as easy as we might have hoped. A number of issues creep up when it es to taking the programming languages everyone used for backend systems and leveraging them to generate markup language suitable for a client. With the arrival of more options on the browser (DHTML and JavaScript coding, for example), the increase in graphic artist talent in the Web domain, and tools that could create plex interfaces using standard HTML, the demand for fancy user interfaces has grown faster than our ability to develop these front ends to our applications. And this has given rise to presentation technology was designed to perform a single task: convert content, namely data without display details, into presentatio n meaning the various user interfaces you see on your phone, PalmPilot, or Web browser. What are the problems that these presentation technologies claimed to solve? Let39。 s take a vs. reworkBesides the separation of content and presentation, another measure of a presentation technology39。 s usefulness is the amount of rework that it eliminates. The divergence of presentation and content enforces a divergence in the roles of those developing the content. A programmer can focus on the raw content presented in the examples above, and a graphic artist or webmaster can attend to the presentation. A slight overlap of roles remains, however, in the process of taking the presentation or markup designed by the artist and applying it to the content the programmer39。 s code the simplest case, the artist supplies the markup, and the developer provides code and also plugs the markup into the presentation technology. The application is started up, and the content magically bees a user interface. Of course, as we all know, development rarely ends there. Next e revisions and changes to the interface and new business rules that must be coded. This is where the true test of the presentation technology39。 s flexibility es into play. While it is usually simple to update the raw content being fed into the pres。