Architectural issues Bridging . There are some features that are fundamental to any technology which supports distributed component development. A component user only needs the IDL of the interface to invoke a function defined in that component. Component developers have the flexibility to develop the component implementation in any programming language of their choice. Given a valid object within a client process, it is the object technology's responsibility to locate the server object in the distributed environment and to control subsequent communication between both distributed objects.
Location transparency is guaranteed through the use of the proxy-stub mechanism.
Uniform Exception Handling schema For any object which runs on a heterogenous distributed environment, a uniform, descriptive, elaborate Exception Handling mechanism is necessary. When a distributed object throws an exception object, the ORB transparently transports this object to the client process. By checking the existence and type of the returned object, the client can determine whether or not an exception occured. Microsoft has however announced that a future version of DCOM would support an exception handling mechanism based on exception objects. Object querying, Object Persistence, Naming, Trading and transaction management for objects are some of the important ones.