COM/DCOM always obeys the factory design pattern. Thus client does not have the authority for allocation or de-allocation of the COM object. Client passes a reference of a pointer to the COM object to server through CreateInstance() or QueryInterface() call. Server allocates the object and returns the pointer to client. Client uses this object and at the end deletes it by Release() call. Client does not have the authority to directly delete the object using free/delete in C++ because it has been allocated by server. So client always calls Release() which decrements the reference count of objects in server-side and when object count reaches to zero it deletes the object from server.
You have viewed 1 page out of 66. Your COM/DCOM learning is 0.00% complete. Login to check your learning progress.
Similar topics related to this section
COM DCOM Interview Questions and Answers :: ALL Interview .com
COM DCOM - COM DCOM Interview Questions
COM interview questions | TechInterviews
COM Interview Questions - CodeProject
Com Dcom Interview Questions - Com and Dcom in Asp Net
ATL Interview Questions and Answers :: ALL Interview .com
ActiveX Interview Questions and Answers :: ALL Interview .com
| #1 webmaster Tue 29 Apr/2014 03:42:47(GMT) || 0 || 0|
We are pleased to inform you that a forum/blog has been incorporated with www.mybestnotes.co.in. You are welcomed to add your comments, requests, codes, solutions and feedback to it. Please login(if already a member) or signup(for free) to avail to this facility.
Your message goes here: