R/S (richclient/Server) architecture in enterprise applications-reprint

An EIS (Enterprise Information System) is being developed recently. Many colleagues believe that the B/S technical architecture should be used.ProgramNo client deployment is required, and maintenance is simple. The client can be easily used with any browser, regardless of the WAN or LAN.

Objective analysis: the current structure is relative to the B/S structure (there is no "opposition" here. In fact, many enterprise applications use multiple technical architectures at the same time) when the R/S architecture is implemented based on DOTNET, the B/S architecture is ineffective.

First, based on the WebService implementation scheme, winforms client programs can run on the wide area network using HTTP like clients in the B/S architecture, the current R/S architecture application has a popular name: RIA (rich Internet application); at the same time, it can also run on. net remoting solution to improve the performance in the LAN.

second, with reference to Microsoft's smartclient concept, the winforms client can make full use of client resources to provide users with a better interactive experience and provide offline processing capabilities, these are all beyond the B/S architecture. Some people will say that the user running the winforms client needs to install additional. NET Framework. In fact, to implement some advanced functions such as DHTML on the B/S client, the browser version is also required, can users upgrade their browsers at this time? On the other hand, the. NET Framework has been integrated into the operating system, just like the current Windows2003, there will be no additional installation problems at that time. However, some people may say that B/S programs can be cross-platform. So I want to ask, is it true that it can be cross-platform ?! That is the "maximum common divisor" model, which sacrifices many platform-related functions. Think about it, the implementations of different browsers are different, not to mention the operating system. In addition, the ongoing mono project is likely to be the first to implement cross-platform. NET Framework. Besides, Microsoft wants to develop a Java virtual machine, which is not a piece of cake. It depends on its market strategy!

Finally, for programming implementation, the R/S architecture program can easily implement the same function,CodeThe structure is clearer, which is a great temptation for me! In addition, I think Microsoft's smartclient concept is very good, but it is too complicated in CAS (code access security), which brings additional burden to the configuration. My current implementation strategy is to first install the minimum installation package of the system on the client through non-contact deployment (just like QQ Games)J, Many programs use this solution .), Create a custom download component (which requires version comparison). This is indeed more than the B/S program, but to get all the other benefits, this sacrifice is definitely worth it, and it's not a big sacrifice.J

Looking at the market, for now, the B/S and R/S architectures are indispensable solutions for enterprise applications, but the boundaries between the two are becoming increasingly vague, we don't have to argue about advantages or disadvantages. I just want to explore better enterprise application solutions with you. Hope to enlighten me!