Shared memory provides the fastest method of interprocess communication, because it processes read and write messages at the speed of memory transfers.
共享内存提供了最快的进程间通信方法，因为它以内存传输的速度来处理读写消息。
Interprocess communication with Stream pipes.
使用流管道的进程间通信。
Interprocess communication using message queue.
使用消息队列实现进程间通信。
Interprocess communication is not allowed.
进程内通讯不可以。
Interprocess Communication is the core feature of Distributed System.
进程间通信是所有分布式系统的核心功能。
The Shared memory is used to implement an interprocess communication media.
共享内存用于实现进程间通信媒介。
Unified interprocess communications, even across heterogeneous processes.
统一的进程间通信，即便是跨越不同种类的进程。
UNIX provides a number of technologies for such interprocess communication.
UNIX为实现这样的进程间通信提供了多种技术。
You're talking about interprocess communication here, with emphasis on process.
这里讨论的主题是进程间通信，重点在进程上。
Thus, by sticking to a synchronous model, interprocess communication can be achieved.
因此，通过采用一个同步模型，就可以实现进程间通信。
A related principle is "no interprocess communication" for basic system services.
相关的定理是基本的系统服务没有内部进程间通信。
Named pipes can be used for interprocess communication locally or over a network.
命名管道可用于本地或网络上的进程间通信。
You will need to use an interprocess communication (IPC) mechanism between these two threads.
在这两个线程之间需要使用一种进程间通信(IPC)机制。
The queue may be removed using an explicit call to boost::interprocess::message_queue::remove.
可以通过显式地调用boost::interprocess::message_queue::remove 删除队列。
Now, let's explore another popular mechanism for interprocess communication: the message queue.
现在，研究另一种流行的进程间通信机制：消息队列。
For most programmers, interprocess communication (IPC) is synonymous with using the Socket API.
对于大多数程序员而言，进程间通信(IPC)就等于使用SocketAPI。
It can be interprocess communication if the server and the client are on the same computer.
如果服务器和客户在同一台计算机上，则通信可在进程之间进行。
Now let's look at using Shared memory and caching of events for interprocess communications.
现在让我们来看一下如何使用共享内存和事件的缓存进行进程间通信。
The simplest mechanism for interprocess communication is reading and writing data across channels.
进程间通信最简单的机制就是通过通道读写数据。
Interprocess communication is not allowed. This includes pipes, semaphores, and Shared memory.
进程内通讯不可以。这包括管道，信号，和共享内存。
Table 1 below summarizes the forms of interprocess communication available on a typical UNIX system.
表1总结在典型的UNIX系统上可用的进程间通信形式。
The initial implementation of the broker pattern provided intra - and interprocess communication.
中介模式的初期实现提供了进程内部和进程之间的通信。
Shared memory is the fastest of the interprocess communications options available and is quite flexible.
共享内存是速度最快的进程间通信技术，而且非常灵活。
This is because POSIX allows this possibility to native interprocess communication implementations.
这是因为POSIX允许这种可能性，即原始的进程间通信实现的可能性。
Ignoring inter host applications, let's look at Shared memory for interprocess communication on the same host.
现在不考虑主机间应用程序通信，看看如何通过共享内存在同一主机上进行进程间通信。
With the advent of the Microsoft Win32 API, interprocess subclassing was discouraged and made a bit harder to code.
随着微软Win32API的到来，进程间子类化不再被鼓励使用并愈发变得困难起来。
We illustrate how to achieve interprocess communication (IPC) can also be achieved, using the second design pattern.
然后阐述如何使用第二种设计模式来实现进程间通信（IPC）。
The company creates a new IM tool that relies on named pipes (or channels) for interprocess communication (IPC).
公司开发了一个新的IM工具，该工具依赖命名管道(或通道)来进行进程间通信(IPC)。
Remoting technologies such as EJB or CORBA mistakenly attempted to apply O-O principles to interprocess communications.
诸如ejb或CORBA这样的远程技术错误之处在于，试图将OO原则应用到进程间通信上。
Thus, PTHREAD_PROCESS_SHARED and interprocess POSIX synchronization primitives can be implemented and are now available.
这样，PTHREAD _ PROCESS_SHARED和进程间POSIX同步原语可以被实现，而且现在可用。
应用推荐