What is DCOM?
What are the other com's available with history and different versions?
DCOM is an abbreviation of Microsoft’s Distributed Component Object Model and it is useful in enabling the software programs to communicate easily over the entire network. It is an additional extension of the COM that enables the different COM components to easily communicate along the networking boundaries.
All the traditional COM elements can just perform the inter-process communication process among the networking boundaries on the similar machine. The DCOM, on the other hand, makes use of the RPC means to evidently send and receive any particular information across the COM elements that mainly include clients and servers that are working over the same network.
DCOM was formerly known as Network Object Linking Library that is Network OLE in short. It was first made available in the year 1995 and 1996 for Windows® 95 and Windows®98 operating systems and then was shipped for Windows® 2000 and recent versions.
DCOM is useful in serving all the
purposes that are to be served by IBM's DSOM protocol which is one of
the most popular implementation and execution of CORBA. Contrasting
CORBA, it runs on numerous operating system where is DCOM is currently
being supported by the Windows®.DCOM is somewhat different from the COM as it is functional for creating such objects that are allocated all across the network, a set of protocols for appealing to the procedures and then securing access to those objects. DCOM wraps the COM; consequently, it is rearward well-suited extension. DCOM also makes use of the RPC protocols.
There has been a controversy that DCOM
can be further used as an opening for Trojans, malware and numerous
other viruses. However, an update has been released by Microsoft that
limits this controversy and fixes all such vulnerabilities. You should
never be disabling the DCOM services as it is one of your system’s
critical and significant services. Before disabling, you should know
what you are doing otherwise it may cause serious issues in your system.
You should be updating your Windows® on frequent basis as this will be
saving your system from all kinds of vulnerabilities.Distributed Component Object Model
 |
This article's citation style may be unclear. The references used may be made clearer with a different or consistent style of citation, footnoting, or external linking. Violates Wikipedia:External links: "Wikipedia articles may include links to web pages outside Wikipedia (external links), but they should not normally be used in the body of an article.". (October 2011) |
| This article includes a list of references, related reading or external links, but its sources remain unclear because it lacks inline citations. Please improve this article by introducing more precise citations. (December 2010) |
The addition of the "D" to COM was due to extensive use of DCE/RPC (Distributed Computing Environment/Remote Procedure Calls) – more specifically Microsoft's enhanced version, known as MSRPC.
In terms of the extensions it added to COM, DCOM had to solve the problems of
- Marshalling – serializing and deserializing the arguments and return values of method calls "over the wire".
- Distributed garbage collection – ensuring that references held by clients of interfaces are released when, for example, the client process crashed, or the network connection was lost.
- Aggregating hundreds or potentially tens of thousands of references to objects held by clients of interfaces at a single host, into a single "ping" function, in order to minimise bandwidth utilisation.
One of the key factors in solving these problems is the use of DCE/RPC as the underlying RPC mechanism behind DCOM. DCE/RPC has strictly defined rules regarding marshalling and who is responsible for freeing memory.
DCOM was a major competitor to CORBA. Proponents of both of these technologies saw them as one day becoming the model for code and service-reuse over the Internet. However, the difficulties involved in getting either of these technologies to work over Internet firewalls, and on unknown and insecure machines, meant that normal HTTP requests in combination with web browsers won out over both of them. Microsoft, at one point, attempted and failed to head this off by adding an extra http transport to DCE/RPC called ncacn_http (Network Computing Architecture, Connection-based, over HTTP). This was later resurrected to support a Microsoft Exchange 2003 connection over HTTP.
0 comments: