[Go] understanding of fat clients and thin clients

Http://blog.sina.com.cn/s/blog_572390880100oo86.html

The difference between C/s

Did you say that the FAT client is equivalent to a C/s structure, while the thin client is equivalent to a B/s structure

The FAT client and thin client are relative. The difference is whether there is a large number of business logic to be placed on the client, C/s structure, the main logic program placed on the client, many times the server refers to the database server. So it's a fat client.

In the B/s structure, the business logic is placed on the server. The client has only one browser, and the server sends it to the client only with strings that follow the HTML rules, of course, if you use an applet or something, it's equivalent to putting some business logic on the client.

World of Warcraft is a typical fat client, and cat travels are typical thin clients.
------------------------------End

Above are the traditional sense of fat thin client, with The rise of Ajax represents the era of the fat client is coming again,

I use the Ajax method to develop a time of the web system, feel the development of the server has been greatly reduced, the main work in JavaScript, even the table is created in the client, the client is a big fat, think of the previous development of applications, basically in the client coding, The feeling is back to that era, which is probably the political spiral of upward meaning it.

(stand-alone) → (fat client + server) → (thin client + server) → (fat client + server)

I think that Ajax has a big advantage is to reduce the server-side pressure, put a lot of work on IE to complete, in fact, is a diversion of the work of a method, basically represents the future direction.

Http://www.yuyanjia.com/augur-61885-1.html

Thin clients and rich clients are two relative concepts. There are two ways of classifying:

1.B/S structure of the network application with the C/s structure of the application, can be called thin client and rich client respectively.

(1) Under this rich client, the client is responsible for most of the business logic processing, in addition to displaying the UI interface of the program to the user for interaction. A typical rich client application consists of one or more applications running on the server and client PCs, with a rich, interactive user interface installed on the client PC, where users can view and manipulate data, handle business transactions, and so on, as clients share part of the server or all of the business logic's processing , so that the client is very "bloated", so called the fat client, also known as the rich client. The server section generally focuses on data access operations, while also dealing with some or all of the business logic.

Advantages: can reduce the pressure on the server, reduce the server performance requirements.

Disadvantage: The requirements of the client machine is relatively high, the client's deployment is not convenient, when the business logic of the program changes, the client update is inconvenient.

(2) This type of thin clients (thin client), mainly refers to the B/s structure of the Web application. is actually a variant of the C/s structure, it will be the client program in the C/s structure, unified as a browser (broswer), the browser only resolves the standard HTML to display the user interface. In this way, the server is responsible for processing business logic and data access, and then the processed results are sent to the client in HTML, the client is responsible for displaying the results to the user, the client in addition to responsible for some data validation and organization, basically do not handle any business logic, only focus on the user interface display, This makes the client look skinny, so it's called a thin client.

2. In this classification, the rich client should exactly be called the Rich Internet application (Rich Internet applications,ria), the thin customer refers to the B/s structure of the Web application.

(1) In this rich client (RIA), the use of highly interactive rich client technology to provide users with a higher and more comprehensive network experience. Ria integrates the interactivity of desktop applications with the deployment flexibility and cost analysis of traditional Web applications to create a single, complete user experience. Rich client technology makes it possible to create a RIA that provides a runtime environment to host a compiled client application that is a file that is published using the HTTP protocol. Client applications use an asynchronous C/s structure to connect to an existing application server, a secure, upgradeable, and well-adapted service-oriented model that is driven by the currently used Web service.

Rich-client technology is constantly being perfected, but it doesn't mean replacing HTML. Instead, it will further extend the browser functionality to provide a more efficient and user-friendly interface. Many RIA runs in the browser, even though it is part of the HTML itself, so the HTML will continue to retain its original role. In addition, because rich-client technology can support moving images, video, audio, bidirectional data communication and create complex forms, it provides an efficient and sophisticated development environment for creating application user interfaces.

Ria Development must have three elements: Rich client technology, server technology, and development tools. Rich client technology leverages the processing power of the local machine to process data without having to send some data to the server for processing, taking advantage of the resources of the local machine. Server technology provides a connection mechanism to rich clients, and as a RIA server technology must inherit from existing server technologies, providing a fast scripting environment that supports database application development, bidirectional data communication, real-time data communication, and even a new server, such as: ColdFusion server, Flash Communication Server, and more. RIA implementations must have a simple and efficient set of development tools, and without a simple and efficient set of development tools, rich client technology and server technology are meaningless. It is due to the C/s structure of RIA that it requires a set of development tools to work together to complete.

Although there are many rich-client technologies, Macromedia Flash Player is widely adopted and has become a network standard for rich-client technologies. Flash Player is already a ubiquitous rich media client that can run on different browsers and operating systems, so it is a cross-platform, cross-operating network client.

Today, with the development of technology, especially the advent of Ajax technology, B/s structure of the Web application also gradually to the fat client development, coupled with the emergence of flex, more speed up the B/s structure of the Web application to the FAT client development. 1-1 are shown for RIA applications.

Resources:

Introduction to Rich client technology. Http://evan2008.blog.51cto.com/509463/107090,2008-10-21.

The difference between a rich guest (also called a fat client) and a thin client. http://hi.baidu.com/loky2008/blog/item/c5f23402697376e209fa9354.html,2010-10-06

[Go] understanding of fat clients and thin clients