What I have experienced is that MY application using the NetMeeting COM
objects
does not end if it has not released all the NetMeeting interfaces it
requested.
But in any cases the NetMeeting application (conf.exe) always survives to
my application.
I don't think there is a way to end it.
I have traced the AddRef() and Release() return values from the NetMeeting
COM interfaces,
but I haven't been able to find out a logical law. Just don't forget that
any method
returning an interface pointer on a NetMeeting COM object has added a
reference on it.
Jerome.
--- Original message ---
From: "Francisco Javier Finez" <[EMAIL PROTECTED]>
I am developing an application with Netmeeting COM objects using NetMeeting
SDK.
Three points only:
- Is conf.exe the only COM object of NetMeeting??
- I gove a problem because when I close the application I have
developed the conf.exe still survives in memory.... Could it be because I
have not Release() all the interfaces I created in the application, and the
component's counter is not to 0??
- If that is the case, what sort of counting uses conf.exe??
Interface counting or component counting?? On being component counting I
could call a for statement to do relese() in one interface until counter
goes to 0 and itself would invoke component's delete method??
-----------------------------------------------------------------------
http://www.meetingbywire.com/Mailinglist.htm for unsubscribe information
-----------------------------------------------------------------------
