dcsimg
Login | Register   
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: Enterprise
Expertise: Intermediate
Aug 3, 1999

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Use the Dual Interface Instead of vtbl only or Pure Interfaces

The COM client and server can communicate with each other in three ways - vtble interfaces, dispinterface or dual interface.

If the component is to be used only from compiled languages such as C and C++, you should use a vtbl or normal COM interface. These vtbl interfaces are much faster than dispinteraces. They are much easier to access from a C++ program.

If your component is to be accessed by VB or Java, you should implement a dual interface. VB or Java can access a dual interface either through dispinterface side or vtbl side. C++ user can also access either side of the dual interface. So, dual interface interfaces are much more versatile to use. Unless you really need to build component at run time, you should avoid pure dispinterfaces.

Jai Bardhan
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date