16.11. Naming, location and binding
So far we have assumed that a process that wishes to engage in communication with a remote process is able to name the destination of the communication. For a single centralized system we assume that the operating system knows the names of all processes and any associated communications endpoints such as ports. A process that wishes to engage in IPC will do so via the operating system. Chapter 7 discussed naming in distributed systems in general terms and a case study (DNS) for objects such as users, mail lists and machines was studied. Here we are concerned with supporting distributed programming where the objects concerned are more dynamic, being associated with currently active processes. One example of ...
Get Operating Systems: Concurrent and Distributed Software Design now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
