1-1 TIBCO General Interface GI处理模型

Processing Model

处理过程

By distributing many of the processes usually handled by centralized application servers to the browser on the client machine, enterprises can deliver full-featured software solutions that simply run in the browser without any need for extra runtime components or plug-ins.

在客户端模式下，分发集中在应用服务器的处理结果到浏览器，企业能够实现所有软件方案功能，简单运行在浏览器上并不需要任何的运行时组件和插件。

TIBCO General Interface is a powerful implementation of model-view-controller (MVC) principles. Unlike server-centric MVC architectures, with General Interface, the view processes are distributed to the web browser. This design removes the view generation work from servers and reduces demands on bandwidth, making applications far more scalable. The design also leverages the power of the client CPU to deliver highly responsive, stateful, full-featured applications in a browser.

TIBCO General Interface是一个强大的mvc概念实现，不像以服务器为中心的mvc架构，General Interface的mvc中的视图部分被完全分配到web浏览器，这个设计从服务器中移除了试图的工作并且减少了带宽，使应用程序更加可扩展，这个设计也平衡了客户端cpu的能力，同时高相应速度、状态、应用程序全部功能三者都在浏览器上实现。

1. Disadvantages of Server-Based MVC Architecture

基于服务器mvc架构的缺点

In a traditional server-based MVC architecture, all processes run on the server. Requests are sent to the controller, models are updated, and the view returns a stream of HTML and data to the browser where it is rendered for the user. This results in system latency and reduced functional possibilities for the end user. The resulting HTML typically comprises 80% presentation instructions and 20% data. The browser is simply an HTML page rendering device.

在传统的基于服务器mvc架构中，所有的处理过程运行在服务器上，请求发送到控制中心(controller),models被更新，接下来view返回一个html字节流，数据发送到浏览器，这些过程都是用户展现功能，这个结果对最终用户来说潜藏和减少了可能的功能（表达不丰富），结果是一个典型的html，由80%结构表达和20%数据组成，浏览器只是一个简单展现html的设备。

Figure 1 Server-based MVC Architecture

2. Rich Internet Application-Based MVC Architecture

基于富客户端(RIA)mvc架构

In a rich Internet application based MVC architecture, view processes are distributed to the browser where they run on the client system. The distributed view employs an MVC architecture of its own, turning the browser into an RIA environment. Because client-side objects generate the HTML, significantly fewer processes need run on the server. Bandwidth is optimized for data. Application performance and scalability are significantly enhanced.

在一个基于富客户端mvc架构中，view处理过程被分配到运行在客户端的浏览器上，view本身就是一个mvc架构，在浏览器的一个RIA环境里运行，因为客户端对象产生html，较少的过程运行在server。

Figure 2 RIA MVC Architecture

General Interface software enables the view portion of the MVC architecture to be distributed to and run on a web browser running on the client system. This approach has the following benefits:

●	Improves application scalability by removing significant server processes

●	Decreases latency by using substantially all the bandwidth to deliver data (instead of a minority of bandwidth for data in the traditional model where HTML markup takes up most of a transmission)

●

Delivers full-featured application performance and rich GUI features to an unmodified web browser, without plug-ins, runtime environments, and extra software to install 在客户端系统上General Interface软件能够使mvc架构的view部分分配到浏览器上运行，这由于下面好处： ×通过移去重要的server处理过程来增强应用程序灵活性 ×减少延迟时间，所有带宽全部用于传递数据。 ×在不修改浏览器、无插件、运行时环境和其他软件不安装情况下展现了所有应用程序的性能和GUI功能。