客户机-服务器场景中的登录。
示例的客户机-服务器体系结构。
定义客户机-服务器架构的涉及范围。
这种配置最终让位给客户机-服务器模型。
This sturdy configuration eventually gave way to the client-server model.
客户机-服务器登录通常用于分布式环境中。
The client-server login is often used in the distributed environment.
最后，您不得不序列化整个客户机-服务器连接上的数据。
Eventually, you're going to have to serialize data across the client-server connection.
对于客户机-服务器应用程序，可行实现很多，从胖客户机到瘦客户机。
With a client-server application, you have a wide spectrum of implementations, from fat client to thin client.
转换本身需要服务器周期；另外，表单可能需要多个客户机-服务器往返周期。
The transformations themselves require server cycles; in addition, the form might require multiple client-server round trips.
ObjectGrid可以通过使用静态集群或动态集群采用客户机-服务器部署模型部署。
ObjectGrid can be deployed with a client server deployment model, using either static clusters or dynamic clusters.
自从低带宽的拨号调制解调器时代以来，浏览器一直限制客户机-服务器连接的数量。
Since the time of limited-bandwidth dial-up modems, browsers have limited the number of client-server connections.
在本文中，我们将阐述一个简单的客户机-服务器应用程序，它发送三条不同的消息。
In this article, we will demonstrate a simple client-server application that sends three different messages.
与传统的使用分布式服务器的客户机-服务器系统不同，大型机不是为单个应用程序而设计的。
Unlike traditional client-server systems utilizing distributed servers, mainframe servers are not designed for single applications.
该模式的应用是在客户机-服务器引入的异步行为以及显式接口引入的各个接口的基础上构建的。
The application of this pattern built upon the asynchronous behavior introduced by client-server, and the interfaces introduced by explicit interface.
它是一种纯嵌入式数据库，可以用在应用程序中，也可以作为更传统的客户机-服务器应用程序的数据库。
It's a purely embedded database that can either be used within an application, or as the database for a more traditional client-server application.
我们将探讨的四项技术尽管都适合基于消息的客户机-服务器应用程序，但是它们的优缺点却有很大差别。
The four technologies that we'll examine, while all suited for a message-based client-server application, differ greatly in their strengths and weaknesses.
他们宣称，未来的计算基础设施将会是一个高度分布的、松散连接的个人电脑和客户机-服务器系统的集合。
The computing infrastructure of the future, they pronounced, would be a highly distributed and loosely connected collection of personal computers and client-server systems.
OTP系统通常采用客户机-服务器模型，在给定的时刻对于给定的用户，在客户端生成相同的一次性密码。
OTP systems are typically built on a client-server model, where at a given time, for a given user, the same one-time passwords are generated on the client side.
在这个案例中，我们用典型的三层客户机-服务器应用程序来研究垃圾收集策略的选择如何影响应用程序性能。
In this case study, we examine how the choice of garbage collection policy affects application performance with a fairly typical three-tiered client-server application.
本教程讨论在基于服务的体系结构中客户机-服务器交互的基本知识，并把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.
瘦客户机应用程序则简化了开发、部署和升级；但是，用户通常都会受累于客户机-服务器间的往来通信所带来的延时。
Thin client applications allow ease of development, deployment, and upgrading; however, the user usually suffers from the delayed ping-pong of client-server communications.
因为UNIX同时运行许多应用程序，所以它是非常适合监视、数据收集、协作和分布式计算以及客户机-服务器应用程序的平台。
Because UNIX runs many applications seemingly at the same time, it's an ideal platform for monitoring, data collection, cooperative and distributed computing, and client-server applications.
例如，分层体系结构、模型-视图-控制器(Model View Controller,mvc)、客户机-服务器甚至SOA。
Think, for example, of layered architectures, model view controller (MVC), client-server, or even SOA.
这些文件包含客户机／服务器应用程序的源代码和已编译的版本，因此，只要把它们放到 CLASSPATH 中，就可以使用了。
These files contain both source and compiled versions of the client/server application, so you can begin using them as soon as they're in your CLASSPATH.
通过一些简单的关键字匹配和客户机——服务器设置，您可以接收所有系统(远程或本地)的屏幕类型通知。
With some simple keyword matching and a client-server setup, you can receive on-screen type notifications of all your systems, remote or local.
因此，理想的选择是通知客户机服务器收到了消息，并在稍后使用一个不同的传输通道发送应答。
So the ideal option is to notify the client that the server received the message and send the reply later using a different transport channel.
这些协议最显著的特征是根据开发人员用于实现的工具选择，客户机、服务器和同级设备可能会大相径庭。
The most appealing feature of these protocols is that clients, servers, and peers can differ dramatically in terms of the developer's choice of tools for implementation.
请注意，HTTP客户机(服务器)可以是发送方也可以是接收方。
Note that an HTTP client (server) could be both a sender and a recipient.
用于REST客户机/服务器交互的规则可以完全通过应用程序要求定义。
The rules that exist for REST client/server interactions can be completely defined by the application requirements.
开发人员使用客户机/服务器模型与集中式VCS系统交互，对本地源代码拷贝的更改只能推回到中心存储库中。
Developers interact with centralized VCS systems using a client/server model, where changes to your local copy of the source code can only be pushed back to the central repository.
这是类似于其他关系数据库的标准客户机/服务器数据库配置，允许出现使用TCP套接字的并发连接。
This is the standard client/server database configuration similar to other relational databases, allowing concurrent connections using TCP sockets.
应用推荐