Post reply

The message has the following error or errors that must be corrected before continuing:
Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.

Note: this post will not display until it's been approved by a moderator.

Name:
Email:
Subject:
Message icon:
Verification:
Please leave this box empty:

Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:

shortcuts: alt+s submit/post or alt+p preview

Topic Summary

Posted by sukishan
 - Aug 13, 2009, 06:31 PM
Interfaces isolate the client from the server
One of the cardinal rules of COM is that you can only access a COM object through an interface. The client program is completely isolated from the server's implementation through interfaces. This is an extremely important point.

The client program knows nothing about the COM object or C++ class that implements the COM object. All it can see is the interface. The interface is like window into the COM object. The interface designer allows the client to see only those parts of the object that he or she wishes to expose. Figure 2-1 illustrates how all client access to the COM object is funneled through the interface.

The notation used here, a small circle connected by a stick, is the conventional way to draw a COM interface. There are many important rules associated with interfaces. While critical for understanding the details how COM works, we can leave them until later. For now, we'll concentrate on the broad concepts of interfaces.
IT Acumens Web Designing Chennai | GinGly :: SMS Backup | CineBuzz :: Latest Cinema News | My Kids Diary :: Kids magical moment
Copyright 2005 - 2019 :: IT Acumens :: All Rights Reserved.
ITAcumens Forum with 2 lakhs post running for 14 years - Powered by IT Acumens Dedicated Server