Content deleted Content added
m Robot-assisted disambiguation (you can help!): Java programming language |
m Robot-assisted disambiguation (you can help!): C programming language |
||
Line 6:
As part of the formation of OSF, various members contributed many of their ongoing research projects. At the time, network computing was quite popular, and many of the companies involved were working on similar RPC-based systems. By re-building these various utilities on a single "official" RPC mechanism, OSF could offer a major advantage over SVR4, allowing any DCE-supporting system (namely OSF/1) to interoperate in a larger network.
The DCE system was, to a large degree, based on independent developments made by each of the partners. DCE/RPC was derived from the ''Network Computing System'' (NCS) created at Apollo Computer. The naming service was derived from work done at Digital. DCE/DFS was based on the [[Andrew File System]] (AFS) originally developed at [[Carnegie Mellon University]]. The authentication system was based on [[Kerberos (protocol)|Kerberos]], and the authorization system based on [[Access Control List]]s (ACLs). By combining these features, DCE offers a fairly complete [[C (programming language)|C]]-based system for network computing. Any machine on the network can authenticate its users, gain access to resources, and then call them remotely using a single integrated [[Application Programming Interface|API]].
Distributed computing never really caught on as much as had been hoped for in the late 1980s and early 1990s. The rise of the [[Internet]], [[Java (programming language)|Java]] and [[web services]] stole much of its [[mindshare]] through the mid-to-late 1990s, and competing systems such as [[CORBA]] muddied the waters as well. Perhaps ironically, one of the major uses of DCE/RPC today are [[Microsoft]]'s [[Distributed_component_object_model|DCOM]] and [[ODBC]] systems, which use DCE/RPC (in [[MSRPC]]) as their network transport layer.
| |||