[Foreword:] Java software designers and managers often face this problem: when developing applications, it should be selected in three technologies of Swing, HTML, XML. In this article, I will share my experience with the majority of readers in these three technologies, and choose some standards and techniques for which technology chooses in Java application software development. At the end of the article, it will also introduce a new way to integrate java swing and html.
Compared to existing technologies, Java has obvious advantages, so it has established dominance in the development of server-side application software. However, since each application has several forms of user interfaces and front-end expression forms, many of us have a bad impression of Java technology in the client, so HTML in the client's development seems to have Become a unique choice. The actual situation is that there is only an HTML in the development of the client application, and we will discuss the solutions of three user interfaces based on Java-based application development. I will first discuss the advantages and disadvantages of HTML and JSP and Servlet, and then discuss one of Java initial goals: interactive Internet through the GUI applet. Finally, we will discuss XML and other techniques that are derived from it. Most readers in the JSP / Servlets environment have written servlets, developed JSP applications, and clear the advantages and disadvantages of HTML-based user interface. The biggest reason to choose HTML is still its extensive platform adaptability, the basic HTML is standardized, although it is boring, but it can work well. Since the HTTP / HTTPS protocol is very simple, development of applications can be well adapted to a variety of network configurations and firewalls. But this is cost, HTML lacks interactive with users, and the response to users must be connected to the server. As a programmer, we have been pursuing simplicity and making the developed software suitable for all browsers? However, simplicity is not always good, simply, JavaScript can achieve less complex interactibility compared to static HTML, but it is still uncomfortable for developing complex user interfaces. Unless you have a high-speed internet connection, you must have anxiously wait for the experience of loading a web page. Although the thin client provides some good non-interactive user interface, the traditional fat customer terminal is generally smarter than them. For example, the front end of Netscape Communicator and MS Outlook and other emails is better than user affinity than Internet-based email tools. Developing an HTML front-end application with Java is a good choice because HTML provides a cross-platform content transmission capability. Programmers can develop server-side applications running on any operating system platform using Java Servlets and JSP. At the same time, considering the support of many Java APIs and its extensive server developers, Java is an ideal choice for developing scalable internet sites. All in all, the HTML front-end development tools using servlets and JSP are well developed in a very good way, but when the behavior of the user needs to make a rapid response to the complex application of high-speed processing on the data, this method is not large. ideal.
