Comparison of b/S and C/s architectures in Web applications

This period of time rather depressed, feel the process of doing this line is too boring, and seems to be less and less life circle. Simply to write something about some of the items that have been touched on before, is to do a summary and memorial.

Currently, many vendors are trying to use web-based applications for enterprise management (e.g. ERP, project management EPM, CRM, MRP ... From the general architecture of these applications, generally can be divided into C/s or B # Two, of which B/s is currently more popular form, then I will summarize the advantages of this web browser for the client:

• Use of this architecture to develop applications that do not require the acquisition or opening of hardware terminals, as long as there is a PC and can be used where the Internet.

• Software upgrades, maintenance work should only be done on the server, without the maintenance of each client.

Compared with c/s, there are more open standards and more easy to realize cross-platform.

But it is not said that using C/s is falling behind the outdated, the following is my summary of the use of C/s advantages:

• Not subject to IE or other Web browsers, you can better integrate with the operating system, such as to achieve the control of peripheral hardware.

• Some functions can be run on the client machine, unlike the B/s program, the function is all to request server processing.

• The internet is not necessarily required, and the data is relatively stable and secure.

In general, both architectures have their advantages and disadvantages, mainly to see what type of application specific development.