分布式计算原理与应用DistributedComputing第二章课件.ppt

Distributed Computing, M. L. Liu Interprocess Communications Mei-Ling L. Liu IPC – unicast and multicast In distributed computing, two or more processes engage in IPC in a protocol agreed upon by the processes. A process may be a sender at some points during a protocol, a receiver at other points. When communication is from one process to a single other process, the IPC is said to be a unicast. When communication is from one process to a group of processes, the IPC is said to be a multicast, a topic that we will explore in a later chapter.  Unicast vs. Multicast Interprocess Communications in Distributed Computing Operations provided in an archetypal Interprocess Communications API Interprocess Communication in basic HTTP Event Synchronization Interprocess communication requires that the two processes synchronize their operations: one side sends, then the other receives until all data has been sent and received. Ideally, the send operation starts before the receive operation commences. In practice, the synchronization requires system support. Synchronous vs. Asynchronous Communication The IPC operations may provide the synchronization necessary using blocking. A blocking operation issued by a process will block further processing of the process until the operation is fulfilled. Alternatively, IPC operations may be asynchronous or nonblocking. An asynchronous operation issued by a process will not block further processing of the process. Instead, the process is free to proceed with its processing, and may optionally be notified by the system when the operation is fulfilled. Synchronous send and receive Asynchronous send and synchronous receive Synchronous send and Async. Receive - 1 Synchronous send and Async. Receive - 2 Synchronous send and Async. Receive - 3 Asynchronous send and Asynchronous receive Event diagram Blocking, deadlock, and timeouts Blocking operations issued in the wrong sequence can cause deadlocks. Deadlocks should be avoided. Alterna