Client Interaction Technology Overview

Client Interaction Technology Overview

With the increasing variety of network applications, client interaction technologies have sprung up and blossomed everywhere. With the support of these technologies, our Internet world has become more diverse. A browser, needless to say, is a simple animation effect, that is, an Office application can be used smoothly. Thanks to the rapid development of client interaction technology. Even the development trend of client interaction technology is that it can take the browser as the carrier or separate applications from the browser.

In general, the current client interaction technology is divided into the following major categories;

1. Microsoft series: ActiveX and Silverlight

2. Java series: Java Applet, RCP (RAP, GWT), JavaFX

3. Adobe series: flash (flex), ActionScript, air

4. Html series: ajax (asynchronous IO), html5

   1. microsoft Series

   1) ActiveX was very popular 10 years ago. At that time, the controls were very simple. Many complex services are encapsulated into ActiveX controls. However, there are several problems: 1. Only Internet Explorer is supported. Some other browsers now support Internet Explorer, but they can only be said to have Internet Explorer compared with the original environment, the effect is different. 2. A digital signature is required. However, the security level of IE can be set, so security is exposed. It can only be said that the idea is good, but the effect has become a chicken ribs.

   2) Silverlight

   Silverlight is a cross-browser, cross-platform plug-in provided by Microsoft. It provides a good multimedia experience and rich interactive application experience for the Web. Based on the. NET platform. It can be run independently or on a browser.

   Mainly based on the following two technologies:

   XAML (eXtensible Application Markup Language) -- display UI layout

   WPF (WindowsPresentation Foundation)-user interface framework

   Silverlight delivers excellent video and animation effects and supports hardware acceleration.

   Silverlight supports windows and IOS, ie, firefox, and safari.

   Silverlight does not have security issues like activex, and SEO is also supported. Website developers are preferred.

   Rich Silverlight controls and support for third-party and custom controls.

   2. java Series

   1) Java Applet: a java program on a webpage. Use awt as the graphics library. The HTML file code of a webpage containing an Applet contains a pair of tags such as <applet> and </applet>. When a web browser supporting Java encounters this pair of tags, the corresponding small application code will be downloaded and the Applet will be executed on the local computer. This was used in the previous google programming contest platform. To run a Java applet, you must first install the Java virtual machine, and then download the applet for the first time. I don't need to use much of it now. It can only be seen in some internal enterprise management systems developed in the past.

   2) RCP. The RCP here refersEclipse RCP.RCP provides a variety of interface controls, which makes it easier to develop desktop applications based on Java. RCP makes full use of the advantages of plug-in systems and is the best practice for building plug-in systems based on OSGi. The Eclipse RCP project replaces AWT and Swing in the Java standard with the SWT graphics library and toolkit. SWT directly calls the graphics library of the operating system, so that the LOOK and Feel of Java applications are exactly the same as those of the operating system. More importantly, direct calls to local methods greatly increase the speed of running SWT-based Java applications. Of course, SWT also has inherent shortcomings. It is not a standard java control library and has a low market share. At the same time, its performance on ios is not good, but it is still available on windows.

   RAP (EclipseRich AjaxPlatform): RAP allows developers to use a wide range of Java libraries and Eclipse APIs to build browser-based Ajax applications. RAP mainly runs on the server. Since RAP runs on the server, you can access a wide range of Java APIs and use the famous Eclipse plug-in model through OSGi. The main difference between RAP and RCP is plug-in dependency and application entry point (IEntryPoint ).

   GWT (GoogleWeb Toolkit) allows Java to write code for Internet-rich applications. GWT runs on the client. GWT is similar to a web SWT application.

    

   3) JavaFX: JavaFX will become the mainstream graphic user interface development library on the Java platform. However, in the rich client field, due to competition in the other three series, the market share is still very small, and it is difficult to estimate in the future. In terms of component appearance, JavaFX2.0, a set of graphical user interface library, also adopted a more popular approach, that is, CSS is used to define the appearance of an application. JavaFX2.0 also introduced the Interface Description Language FXML. javaFX 2.0 began to use java as the development language rather than the previous JavaFX script. in future development, AWT and Swing should gradually fade out of the desktop application development field of view. JavaFX should play a role in the internal system of the enterprise.

    

   3 Adobe series:

   1) flash (flex): The Flash programming model is based on the timeline, while Flex is based on the form. One serves designers and the other serves developers.

   2) ActionScript: Develop the programming script language of flash or flex.

   3) Adobe Air is a video playing platform developed using Adobe Flash technology. Familiar example: sina Weibo air.

   Advantages: 1) cross-platform (cross-operating system, cross-browser) 2) lower technical threshold: Only web development technology is required. 3) it can be run offline and occasionally connected to the network. 4) flash-based user experience is better

   Disadvantages: 1) user experience and interactive operations are insufficient than those of desktop applications, and many applications require desktop applications to be installed. 2) virtual machines need to be installed

    

    

   4.html Series

   1) ajax

   This is the current mainstream. The basis of Web2.0. This technology enables asynchronous local update of web pages. All browsers on the market are supported. Mainstream js frameworks have also been encapsulated. Streaming Media Processing is insufficient.

   Asynchronous IO-is a socket connection method that enhances the interaction between client and server for Synchronous IO. It is often used in various distributed, instant messaging and middleware systems. It is an efficient and highly scalable communication architecture.

   2) Html5 is the future trend. Solve client interaction at the browser level, instead of the three categories mentioned earlier, and enhance interaction through plug-ins. It supports multiple devices across platforms.

   Html5 mainly includes some new ui controls, such as multimedia player webplayer and canvas; added support for websoket, which is a fundamental disruption to asynchronous IO; added webwork, high-performance computing and page display can be separated by threads without affecting the user experience. With the addition of css3 support, 3D effects are more supported in the presentation style. Html5, through the history feature, even solves the inherent deficiency that ajax cannot modify URLs. When the cloud era is approaching, Html5 will represent the future. Of course, all these needs to be carried out one by one through the baptism of the market.

    

    

   All in all, the client interaction technology is constantly moving forward. Nothing else, just because it will bring more real user experience to users in the Internet era.

What is the rich client interaction technology?

If you want to know what the rich client interaction technology is, you must first understand the difference between the fat client (also called the rich client) and the thin client.

Network applications have gone through the development process from fat clients to thin clients. Fat clients are compared with traditional network applications in the C/S structure,
Thin clients are generally compared with B/S-structured Web applications.

Fat client application
Compared with a thin client, a fat client divides the processing process of an application into two parts: the client and the user's desktop
The executed processing and some centralized processing of the server. The client of the fat client application is not only responsible for displaying the UI of the program
In addition to interaction with users, most of the business logic is also responsible for processing. This type of application requires that the client has
Capability, which has high requirements on the client machine, but can reduce the pressure on the server and the performance requirements of the server. Typical
The fat client application contains one or more applications running on the server and the client PC. The client PC has a rich set of interactive user interfaces,
Through this interactive interface, you can view and operate data, process business transactions, and share some or all of the server's business logic. (In this way, the fat client is very "bloated ", so it is called a fat client or a rich client ).
The server generally processes data access operations in a centralized manner, and is also responsible for processing part or all of the business logic.

Thin client application
A thin client application is a Web application in the B/S structure. It is a variant of the C/S structure.
The browser parses only standard HTML to display the user interaction interface. In this way, the server is responsible for processing the business logic and data access,
Then, the processed results are sent to the client in HTML format. The client is responsible for displaying the results to the user. The client is not only responsible for verifying and organizing some data,
Basically, it does not process any business logic and only focuses on the display of user interaction interfaces. (thin clients are very thin, so thin clients are called thin clients)

Nowadays, with the development of technology and the emergence of ajax technology, web applications with B/S structure are gradually developing towards fat clients. In addition, the emergence of flex has become a rising star, it accelerates the development of B/S-structured web applications to fat clients.
To understand rich client interaction technology, you must first write a traditional web application and then use ajax to compile a rich client web application.
By the way, ajax is actually capable of sending asynchronous requests, which is her biggest function.

Server-side development that interacts with Android clients

C/S.
B/S. The Client can parse the returned data.
B/S, JAVA PHP ASP. NET can all
XML return, JSON return can all be