【正文】 和客戶群，各家企業(yè)都說自己的管理軟件架構(gòu)技術(shù)功能強大、先進、方便，都能舉出各自的客戶群體，都有一大群文人墨客為自己搖旗吶喊，廣告滿天飛， 可謂仁者見仁，智者見智 C/S 架構(gòu)軟件的優(yōu)勢與劣勢 (1)應(yīng)用服務(wù)器運行數(shù)據(jù)負(fù)荷較輕。 最簡單的 C/S 體系結(jié)構(gòu)的數(shù)據(jù)庫應(yīng)用由兩部分組成，即客戶應(yīng)用程序和數(shù)據(jù)庫服務(wù)器程序。二者可分別稱為前臺程序與后臺程序。運行數(shù)據(jù)庫服務(wù)器程序的機器，也稱為應(yīng)用服務(wù)器。一旦服務(wù)器程序被啟動，就隨時等待響應(yīng)客戶程序發(fā)來的請求；客戶應(yīng)用程序運行在用戶自己的電腦上，對應(yīng)于數(shù)據(jù)庫服務(wù)器，可稱為客戶電腦，當(dāng)需要對數(shù)據(jù)庫中的數(shù)據(jù)進行任何操作時，客戶程序就自動地尋找服務(wù)器程序，并向其發(fā)出請求，服務(wù)器程序根據(jù)預(yù)定的規(guī)則作出應(yīng)答，送回結(jié)果，應(yīng) 用服務(wù)器運行數(shù)據(jù)負(fù)荷較輕。 (2)數(shù)據(jù)的儲存管理功能較為透明。 在數(shù)據(jù)庫應(yīng)用中，數(shù)據(jù)的儲存管理功能，是由服務(wù)器程序和客戶應(yīng)用程序分別獨立進行的，前臺應(yīng)用可以違反的規(guī)則，并且通常把那些不同的 (不管是已知還是未知的 )運行數(shù)據(jù)，在服務(wù)器程序中不集中實現(xiàn)，例如訪問者的權(quán)限，編號可以重復(fù)、必須有客戶才能建立定單這樣的規(guī)則。所有這些，對于工作在前臺程序上的最終用戶，是“透明”的，他們無須過問 (通常也無法干涉 )背后的過程，就可以完成自己的一切工作。在客戶服務(wù)器架構(gòu)的應(yīng)用中，前臺程序不是非?！笆菪　?，麻煩的事情都交給了服務(wù) 器和網(wǎng)絡(luò)。在 C/S 體系的下，數(shù)據(jù)庫不能真正成為公共、專業(yè)化的倉庫，它受到獨立的專門管理。 (3) C/S 架構(gòu)的劣勢是高昂的維護成本且投資大。 首先，采用 C/S 架構(gòu)，要選擇適當(dāng)?shù)臄?shù)據(jù)庫平臺來實現(xiàn)數(shù)據(jù)庫數(shù)據(jù)的真正“統(tǒng)一”，使分布于兩地的數(shù)據(jù)同步完全交由數(shù)據(jù)庫系統(tǒng)去管理，但邏輯上兩地的操作者要直接訪問同一個數(shù)據(jù)庫才能有效實現(xiàn)，有這樣一些問題，如果需要建立“實時”的數(shù)據(jù)同步，就必須在兩地間建立實時的通訊連接，保持兩地的數(shù)據(jù)庫服務(wù)器在線運行，網(wǎng)絡(luò)管理工作人員既要對服務(wù)器維護管理，又要對客戶端維護和管理，這需要高昂的投 資和復(fù)雜的技術(shù)支持，維護成本很高，維護任務(wù)量大。 其次，傳統(tǒng)的 C/S 結(jié)構(gòu)的軟件需要針對不同的操作系統(tǒng)系統(tǒng)開發(fā)不同版本的軟件，由于產(chǎn)品的更新?lián)Q代十分快，代價高和低效率已經(jīng)不適應(yīng)工作需要。在 JAVA這樣的跨平臺語言出現(xiàn)之后， B/S 架構(gòu)更是猛烈沖擊 C/S，并對其形成威脅和挑戰(zhàn)。 B/S 架構(gòu)軟件的優(yōu)勢與劣勢 (1)維護和升級方式簡單。 目前，軟件系統(tǒng)的改進和升級越來越頻繁， B/S 架構(gòu)的產(chǎn)品明顯體現(xiàn)著更為方便的特性。對一個稍微大一點單位來說，系統(tǒng)管理人員如果需要在幾百甚至上千部電腦之間來回奔跑，效率和工作量是可想而知 的，但 B/S 架構(gòu)的軟件只需要管理服務(wù)器就行了，所有的客戶端只是瀏覽器，根本不需要做任何的維護。無論用戶的規(guī)模有多大，有多少分支機構(gòu)都不會增加任何維護升級的工作量，所有的操作只需要針對服務(wù)器進行；如果是異地，只需要把服務(wù)器連接專網(wǎng)即可，實現(xiàn)遠(yuǎn)程維護、升級和共享。所以客戶機越來越“瘦”，而服務(wù)器越來越“胖”是將來信息化發(fā)展的主流方向。今后，軟件升級和維護會越來越容易，而使用起來會越來越簡單，這對用戶人力、物力、時間、費用的節(jié)省是顯而易見的，驚人的。因此，維護和升級革命的方式是“瘦”客戶機，“胖”服務(wù)器。 (2)成本降低，選擇更多。 大家都知道 windows 在桌面電腦上幾乎一統(tǒng)天下，瀏覽器成為了標(biāo)準(zhǔn)配置，但在服務(wù)器操作系統(tǒng)上 windows 并不是處于絕對的統(tǒng)治地位。 現(xiàn)在的趨勢是凡使用B/S 架構(gòu)的應(yīng)用管理軟件，只需安裝在 Linux 服務(wù)器上即可，而且安全性高。所以服務(wù)器操作系統(tǒng)的選擇是很多的，不管選用那種操作系統(tǒng)都可以讓大部分人使用windows 作為桌面操作系統(tǒng)電腦不受影響，這就使的最流行免費的 Linux 操作系統(tǒng)快速發(fā)展起來， Linux 除了操作系統(tǒng)是免費的以外，連數(shù)據(jù)庫也是免費的，這種選擇非常盛行。 比如說很多人每天上 “新浪”網(wǎng)，只要安裝了瀏覽器就可以了，并不需要了解“新浪”的服務(wù)器用的是什么操作系統(tǒng)，而事實上大部分網(wǎng)站確實沒有使用 windows操作系統(tǒng)，但用戶的電腦本身安裝的大部分是 windows 操作系統(tǒng)。 (3) 應(yīng)用服務(wù)器運行數(shù)據(jù)負(fù)荷較重。 由于 B/S 架構(gòu)管理軟件只安裝在服務(wù)器端 (Server)上，網(wǎng)絡(luò)管理人員只需要管理服務(wù)器就行了，用戶界面主要事務(wù)邏輯在服務(wù)器 (Server)端完全通過 WWW 瀏覽器實現(xiàn)，極少部分事務(wù)邏輯在前端 (Browser)實現(xiàn)，所有的客戶端只有瀏覽器，網(wǎng)絡(luò)管理人員只需要做硬件維護。但是，應(yīng)用服 務(wù)器運行數(shù)據(jù)負(fù)荷較重，一旦發(fā)生服務(wù)器“崩潰”等問題，后果不堪設(shè)想。因此，許多單位都備有數(shù)據(jù)庫存儲服務(wù)器，以防萬一。 附件 2：外文原文（復(fù)印件） The Development Of ASP System Structure Develop Web application program using ASP the architecture that must first establish Web application. Now in application frequently with to have two: The architecture of C/S and the architecture of B/S. Client/server and customer end / server hold the architecture of C/S. The customer / server structure of two floor. Customer / server ( Client/Server ) model is a kind of good software architecture, it is the one of best application pattern of work. From technology, see that it is a logic concept, denote will a application many tasks of deposing difference carry out , mon pletion is entire to apply the function of task. On each work main puter of web site, resource ( hardware, software and data ) divide into step, is not balanced, under customer / server structure, without the client puter of resource through sending request to the server that has resource , get resource request, so meet the resource distribution in work not balancedness. With this kind of structure, can synthesize various puters to cooperate with work, let it each can, realize the scale for the system of puter optimization ( Rightsizing ) with scale reduce to melt ( Downsizing ). Picture is as follows: It is most of to divide into puter work application into two, in which the resource and function that part supports many users to share , it is realized by server。 Another part faces every user , is realized by client puter, also namely, client puter is usual to carry out proscenium function , realizes manmachine interaction through user interface , or is the application program of specific conducted user. And server usually carries out the function of backstage supporter , manages the outside request concerning seting up, accepting and replying user that shared. For a puter, it can have double function , is being certain and momentary to carve to act as server , and again bees client puter in another time. Customer / server type puter divide into two kinds, one side who offers service is called as server , asks one side of service to be called as customer. To be able to offer service, server one side must have certain hardware and corresponding server software。 Also, customer one side must also have certain hardware and corresponding customer software. There must be a agreement between server and customer, both sides municate according to this agreement. Apply customer / server model in Inter service , the relation between customer and server is not immutable. Some Inter node offers service on the one hand , also gets service on the other hand from other node。 It is even in one time dialogue course, mutual role also exchanges probably. As in carry out file transmission , if be called as one side who offers file server, is called as one side who gets file customer, when using get or mget order since another node takes file, can think that what self use and it is client puter , is using put or mput order to another node dispatch file can again think the machine that used self is server. Multilayer customer / server structure Along with the development of enterprise application, recently, have again arisen a kind of new multilayer architecture, it applies customer end to divide into two minutes: Customer application and server apply. Customer application is the part of original customer application , is another and partial to have been transfered to server to apply. New customer application takes the responsibility for user interface and simple regular business logic and new server application resident core , changeable business logic. Therefore its structure has bee new ( Client application + Server application )/Server structure. Following picture shows: This kin