This sturdy configuration eventually gave way to the client-server model.
这种配置最终让位给客户机-服务器模型。
It is based on a client-server protocol.
它是基于客户-服务器协议。
Authenticate the client side of a client-server connection.
对客户端-服务器连接的客户端进行身份验证。
General strategy: Client-server strategy.
一般策略：客户机——服务器策略。
Client communicate to server with session key.
客户端使用会话密钥与服务器通信。
Client can't locate the server.
客户机无法定位服务器。
Launch an app on X Client to display on X server.
在X客户机上启动应用程序以在X服务器上显示。
MDM Server also has several client components.
MDMServer也含有多个客户机组件。
We'll test this configuration with a remote client installed on Application Server 5.1.2 and 6.0.2.
我们将使用安装在ApplicationServer5.1.2和6.0.2 上的远程客户端来测试此配置。
What happens to the client session data in case the original server crashes?
如果原始服务器坏掉，对这个客户会话数据将会有什么样影响？
After this, the connection between client and server is established.
这样，客户机和服务器之间的连接就建立起来了。
There is no login process specific communication between client and server.
客户机和服务器之间不存在登录过程特定的通信。
Development of both the client and server side can then begin in parallel.
在这种模式下，客户端和服务器端的开发可以并行启动。
You can set up both the client and server software on one machine.
您可以在同一台机器上设置客户机和服务器软件。
Running the Axis client and server.
运行Axis客户机和服务器。
Using this session key, client and server can safely communicate with each other.
使用此会话密钥，客户端和服务器可以安全地相互通信。
This requires easy access to client and server side implementations of the protocol.
这就要求能方便地访问协议的客户机和服务器端的实现。
The simple interaction between client and server is shown in Figure 1.
客户机和服务器之间的简单交互如图1所示。
Start the Team Concert client and server.
启动Team Concert客户端和服务器。
REST never directly refers to any specific communication protocol between client and server.
REST从不直接在客户端和服务器之间引用任何具体的通信协议。
Actual contact of client to the server.
客户端与服务器的实际通信。
Running the Bus client and Axis server
运行总线客户机和Axis服务器
Running the Axis client and Bus server
运行Axis客户机和总线服务器
Let's look at a message exchange between a client and a server.
让我们看一下客户机和服务器之间的消息交换。
Does there end up being redundant logic on the client and the server?
这会导致客户端和服务器上多余的逻辑吗？
The client requests the server for it only when mutual authentication is necessary.
只有在需要进行相互身份验证时，客户机才向服务器请求这个包。
We will perform both server and client authentication.
我们将同时进行服务器和客户端的身份验证。
So much for the basic JSSE server and client code.
基本的JSSE服务器和客户机代码就只有这些。
Then repeat the process on each NIS slave server and client.
然后在每个NIS 从服务器和客户端上重复该过程。
Then repeat the process on each NIS slave server and client.
然后在每个NIS 从服务器和客户端上重复该过程。
应用推荐