 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
 |
|
 |
 |
 |
| |
DC Communication |
Although distributed technologies help distribute the workload, different companies are competing with their own proprietary standards, which could make parts from different vendors non-interoperable. It's either all from one company, or nothing. A distributed computing environment, on the other hand, alleviates this problem. Let's take this from a different perspective. Schools have a standard set of rules and regulations that apply to every classroom, different teachers — depending on the type of class they teach — have their own set of rules. The standard school regulations help maintain an orderly learning environment, so that students and teachers don't get confused with six or seven different sets of rules. Likewise, the variety of standards each computer has in a distributed computing network can wreak havoc when the computers attempt to get along. The Distributed Computing Environment (DCE) — formulated by The Open Group — formalizes technologies such as remote procedural calls and middleware. The Distributed Computing Environment makes sure applications behave consistently across different operating systems and computers. The Distributed Computing Environment set of standards includes other features, such as security, synchronizing of time, a distributed file system, and remote procedural calls. (Caution: do not confuse DCE with middleware! Its main concern is to translate the data that computers send to each other. It might seem eerily similar to DCE, but it's because it's actually a part of DCE.) These specifications help cut down on maintenance costs for different platforms, which wouldn't cooperate with each other without DCE. Plus, it's supported by many companies that provide networking software and network operating systems, including IBM, Digital Equipment, and Microsoft. continued...
| ||||||||
|
©2000 Team DC (Thinkquest Team C007645). Hosted by ThinkQuest. |