ENVS 1500 Chapter Notes - Chapter 20: Common Object Request Broker Architecture, Message Passing, Data Integrity
13 May 2018
School
Department
Course
Professor
ENVS 1500 Chapter 20 Notes – Summary
Introduction
• Most operating systems control these services in such a way as to prevent damage to
the syste o to othe uses’ files ad esouces.
• As another example, output to a screen is performed directly to I/O, rather than through
the file system, on many computer systems.
• These I/O services allow programs to write text and graphics to the screen without
compromising the system.
• Services to programs also include services that are less apparent to the user, but
important nonetheless.
• Inter process message passing allows programs to synchronize their actions to protect
data integrity, to share and exchange data, and even to distribute program processing
among different machines on a network.
• DCOM (Distributed Component Object Model), its extension .NET, and CORBA (Common
Object Request Broker Architecture) are two standards that allow programs to locate
and share objects, either on a system or across a network.
• Remote Procedure Call (RPC) allows a program to call a procedure at a remote location
across a network.
• .NET ad othe euivalet opeatig syste tools also ease a pogae’s task at
creating new programs by providing commonly required program objects and allow
computers on a network to share the processing load.
• Particularly in modern systems, where elegant user interfaces and graphics are the
norm rather than the exception
• The operating system provides a library of powerful service routines for implementing
user interfaces and graphics for individual programs.
• On most modern workstations and personal computers, it is only necessary for a
program to call a series of these routines to maintain control of windows, drop-down
menus, dialog boxes, and mouse events.
find more resources at oneclass.com
find more resources at oneclass.com
