Prepare,Attach and DetachThread for delivering indications

<[email protected]>
Newsgroups gmane.network.open-pegasus.general
Message-ID <[email protected]>
Hi,
   We are developing a indication provider. The problem is, every time
indication is generated, there seems to be an memory leak ( caught
through pmap). We have gone through Pegasus documentation and still not
clear about following usage:-
 
1. Should Provider explicitly do CMRelease the CMPI instance which is
created through CMNewInstance for passing in CBDeliverIndication or
CBDeliverIndication  internally frees it?
 
2. Can AttachThread be called once in the beginning and detachThread at
the termination point when there may be multiple deliver indications in
between ?
 
3. In sample indication provider
(/src/Providers/TestProviders/CMPI/TestIndications), we have found a new
thread is created using  _broker->xft->newThread to attachThread and
deliver indication. But we are calling PrepareAttachThread in
ActivateFilter() and calling CBAttachThread and DeliverIndication in a
native thread context . Is there any harm ? 
 
4. Can PrepareAttachThread be called from a non-cimom generated thread?
 
Thanks
Souvik
 
 

Please do not print this email unless it is absolutely necessary. 

The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. 

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. 

www.wipro.com
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.