These clients are referred to as thick or fat clients because they had a significant portion of the executable code in the client tier (see Figure 2).
这种客户端被称作“胖客户端”，因为这种结构将可执行代码的相当大一部分都放到了客户端一级(参见图2)。
All end users, who use the infrastructure, are seen as part of the client tier (at this point we make no difference between Intranet and Internet applications).
所有最终用户(使用基础设施的人)都可以视为客户端层的一部分(此时我们并不区分内部网和外部网应用程序)。
The presentation tier is the interface from the servers to the client, and is responsible for formatting the output so that it can be displayed on the client.
表示层是从服务器到客户机的接口，它负责控制输出的格式，让输出可以在客户机上显示。
The WebSphere XD use case mainly consists of three tiers which are named client tier, DMZ tier, and middleware tier.
WebSphereXD用例主要由三个层次组成，即客户端层、DMZ 层和中间件层。
Stateful interactions between client and server can be managed on either the Web tier or the business tier.
客户机和服务器之间的有状态交互可以在web层或业务层上进行管理。
It provides a complete example of a CORBA client accessing business-tier EJBs managed by the Geronimo server.
提供了一个完整的CORBA客户机访问Geronimo服务器管理的业务层ejb的例子。
Two-tier thick client applications are easy to develop, but any software upgrade because of changes in user interface or business logic has to be rolled out for all the clients.
尽管2级“胖客户端”应用的开发很简单，但是任何用户接口或者业务逻辑的改变所导致的软件升级都需要在所有客户端上进行。
In a Web application, the client tier is handled by the Web browser.
在Web应用程序中，客户机层由Web浏览器处理。
These services create a model that the presentation tier consumes to create a view to send to a client.
这些服务创建一个模型，表示层利用此模型来创建一个发送到客户机的视图。
In this example Web application, the client (a JSP page in the Web tier) holds a reference to, and calls methods on, an instance of the CustomerSession stateful session EJB component.
在该示例Web应用程序中，客户机(web层中的jsp页面)保存了一个对CustomerSession状态会话ejb组件的一个实例的引用，并调用该实例上的方法。
Because a consumer could be a component on a tier that serves another component, to call it a client component would be confusing.
因为使用者可能是一层中为另一组件服务的组件，所以称之为客户组件会引起混乱。
In this setup, the client bypasses the Web tier and communicates directly with the business tier (session beans) using the IIOP protocol.
在该设置中，客户机绕过了web层，并使用IIOP协议直接与业务层(会话bean)进行通信。
The only differences are the nature of the client and the presentation layer of the middle tier.
惟一的不同点在于客户端的本质和中间层的表示层。
The package's client-side components are usually deployed within a client application or installed on a remote server that is interacting as a client tier.
这个包的客户机端组件通常被部署到客户机应用程序中或者安装在正在作为客户机层进行交互的远程服务器上。
The data tier cannot be accessed directly from the client in the presentation tier.
数据层不能从表示层中的客户端直接访问。
We will create a custom message converter to send a trade creation request message from the client to the middle tier.
我们将创建一个自定义消息转换器，来发送一个从客户端到中间层的关于交易创建的请求消息。
With data binding technology of the multi tier application system based on RDS, the user can do complicated processing on large amount of data interactively from the client computer.
基于RDS的多层应用系统利用数据绑定技术，使用户在客户端能对大量数据进行复杂的交互式处理。
A three-tier enterprise architecture consists of a client tier, middle tier, and a data tier.
一个三层的企业架构由客户机层、中间层以及数据层组成。
Such proven strengths on the client tier can be combined with open source technologies such as PHP, Python, and Ruby to extend the Ajax story into mid-tier application development.
客户端上已经证明有效的这些技术可以与PHP、Python和Ruby等开放源码技术相结合，将Ajax扩展到中间层应用程序开发领域。
Then there was another form of two-tier architecture in which not only the UI but even the business logic resided on the client tier.
此后又出现了另外一种2级结构，在这种结构中，不只是用户接口（UI），连业务逻辑也被放到了客户端一级。
This feature finds particular use in a three-tier system where the Web server and the DB2 client form the middle tier.
该特性尤其适用于由Web服务器和DB2客户机组成中间层的三层系统。
And two-tier systems perform poorly when a fat client must connect to a database over the WAN.
当胖客户机必须通过WAN连接到数据库时，两层系统的性能较差。
If the EJB client and EJB modules are mapped to different application server instances (often referred to as split-tier), then the EJB modules must be invoked remotely using pass by value semantics.
如果EJB客户机和EJB模块被映射到不同的应用服务器实例(通常表示为split - tier)，则必须使用通过值传递的语义来远程调用EJB模块。
Is based on the n-tier model and supports browser users (client node) and mobile users (pervasive user node) accessing back-end applications.
基于n层模型，支持浏览器用户(client节点)和移动用户(pervasiveuser节点)访问后端应用程序。
This approach overcomes the security problems of deploying two-tier systems over the WAN by replicating a native client to a remote user.
通过将一个原生客户端复制给一个远程用户，这种途径克服了通过WAN部署两层系统的安全性问题。
The components can then be used to provide multi-tier client - and server-based enterprise applications.
可以用这些组件来提供多层的、基于客户机和服务器的企业应用程序。
IDE for client tier code development.
用于客户端代码开发的ide。
One important aspect of N-tier development is the ability to exchange entity state between the server and the client. Diego Vega, Program Manager ADO.NET entity Framework, details this further.
N层开发的一个重要方面是在服务器和客户端之间进行Entity状态交换。
In 2-tier Client application models people were even accessing the database directly from the event-handlers.
在两层的客户端应用模型中，人们甚至会直接从事件处理器中访问数据库。
In the client tier, this scenario USES browser-based controls enabled through single-page XHTML user interface elements along with XHR and JSON.
在客户端，这个场景使用基于浏览器的控件，这些控件是通过单页面XHTML用户界面元素以及XHR和JSON启用的。
应用推荐