因为服务器可以是任意数量不同的平台，我们应该预计到客户机和服务器之间的体系结构差异。
Because our server could be on any number of different platforms, we should expect architectural differences between the client and the server.
他们实际上并不关心混合内容、属性、语言独立性或者其他有用的XML特性，他们需要的是从服务器向客户机发送数据结构。
They didn't really care about mixed content, attributes, language independence, or other useful characteristics of XML -- they wanted to send data structures from the server to the client.
从基础结构的角度来说，过去可以构建一个通用的在线游戏服务器基础结构，支持任何能够连网的客户机平台。
From an infrastructure perspective, it used to be the case that you could build an online game server infrastructure that would support any online-capable client platform.
本教程讨论在基于服务的体系结构中客户机-服务器交互的基本知识，并把RPC作为这些原理的一种实现来研究。
This tutorial covers the basics of client-server interactions in a service-based architecture and explores RPC simply as one implementation of those principles.
而DB 2 9.5中新的客户机基础结构对于降低IBM数据服务器解决方案涉及的人员成本起了非常重要的作用。
The new client infrastructure in DB2 9.5 is a key component to lowering the personnel costs associated with an IBM data server solution.
xml格式极为适合结构化和定义良好的数据，在这种情况下，服务器和客户机都完全了解数据的形式。
XML. XML format is excellent for structured and well-defined data in which both the server and the client are completely aware of how the data will look.
客户机应用程序或组件使用JDBC或SQLJ访问EII服务器管理的异类数据，该服务器透明地集成不同种类的数据，并以表结构返回这些数据。
Client applications or components use JDBC or SQLJ to access disparate data managed by an EII server, which transparently integrates heterogeneous data and returns it in a tabular structure.
示例的客户机-服务器体系结构。
分布式关系数据库体系结构(distributed relation database architecture,DRDA)是用于客户机与服务器之间通信的常见协议，它由RuntimeClient提供。
Distributed relation database architecture (DRDA) is the common protocol used for communication between the client and the server, and is provided by the Runtime client.
服务器与Notes客户机拓扑结构如图1 所示。
The topography of servers and the Notes client are illustrated in Figure 1.
所以当感兴趣的数据发生变化时，Grid基础结构(在服务器上)会向客户机发送一个通知消息。
So when the interested data changes, the Grid infrastructure (on the server) will send a notification message to the client.
SOAP客户机将从WSDL文件中读取SOAP结构并与另一端的SOAP服务器协调，所以必须特别关注interoperability。
A SOAP client will read the SOAP structure from your WSDL file and coordinate with a SOAP server on the other end, so you must be very concerned with interoperability.
例如，分层体系结构、模型-视图-控制器(Model View Controller,mvc)、客户机-服务器甚至SOA。
Think, for example, of layered architectures, model view controller (MVC), client-server, or even SOA.
然后客户机就可以在请求资源访问权限时为目标应用服务器生成这个身份标识符（identifier）（而不是更大的PAC结构）。
The identifiers (instead of the larger PAC structures) would then be produced by the client for the target application servers while requesting a resource access.
当订阅某个主题的客户机连接到JMS服务器时，它可以请求适合层次结构特定部分的消息。
When a topic-subscribing client connects to the JMS server, it can request messages that fit into a specific section of the hierarchy. As an example, consider the hierarchy outlined in Figure 3.
改变了客户机在C/S结构中是被动的角色，使得客户机在P2P网络中成为同时具有服务器和客户机功能的节点。
Changing the passive role in C/S structure, the client has the server and the client function in the P2P network.
本文在传统的客户机与服务器之间的软件体系基础上，提出了网络数据驱动模型这一新的结构。
On the basis of the traditional software architecture between client and server, this thesis brings forward the new architecture, which is the network data-driving model.
之前的结构是个人计算机客户带来的专有网络，那被称为客户机-服务器计算。
The previous architecture was a proprietary network with PC clients called client-server computing.
GCRSE在体系结构上利用了节点功能角色的方式，由服务器功能实体、自愿机功能实体和客户机功能实体组成。
Using the node function role approach, GCRSE was composed of three kinds of node: role peers, named server, volunteers and clients.
GCRSE在体系结构上利用了节点功能角色的方式，由服务器功能实体、自愿机功能实体和客户机功能实体组成。
Using the node function role approach, GCRSE was composed of three kinds of node: role peers, named server, volunteers and clients.
应用推荐