Re: CMPI Provider threaded?

I don't believe that OpenPegasus could call a provider in an asynchronous manner, because that not only would require callback function pointers to complete the operations, but could also cause multiple provider instances to corrupt data.
Synchronous is a lot safer.
Some providers are just a front end for a synchronous safe database, but many are not and would not survive synchronous calls.
The standard had to be written for the worst case scenario.
How would OpenPegasus know which providers could handle concurrent calls, and which could not?

 
Kirk Augustin
11821 NW McNamee Rd
Portland, OR 97231


HM: 503-289-4356


>________________________________
> From: Shane Hender <[email protected]>
>To: "[email protected]" <[email protected]> 
>Sent: Thursday, June 6, 2013 6:20 PM
>Subject: CMPI Provider threaded?
> 
>
>
>Hi,
>
>
>I'm writing providers using the CIMPLE/SimpleWBEM C++ interface that sits on top of CMPI.
>
>
>However, I notice that my providers are getting called in a synchronous fashion, I.e., 2 requests to my provider will not get executed concurrently.  Is there something I missed in compiling OpenPegasus to allow this support in the Provider Agent?
>
>
>Thanks,
>Shane.
>
>>________________________________
> 
>Confidentiality Notice: The information contained in this electronic e-mail and any accompanying attachment(s) is intended only for the use of the intended recipient and is confidential and/or privileged. If you and we have a confidentiality agreement or other
 non-disclosure obligations between us, this Notice shall be deemed to mark and identify the content of this email and any attachments as confidential and proprietary. If any reader of this communication is not the intended recipient, unauthorized use, disclosure
 or copying is strictly prohibited, and may be unlawful. If you have received this communication in error, please immediately notify the sender by return e-mail, and delete the original message and all copies from your system. Thank you.
>
>IRS Circular 230 Disclosure: To ensure compliance with requirements imposed by the IRS, please be advised that any U.S. federal tax advice contained in this communication (including any attachments) is not intended or written to be used or relied upon, and
 cannot be used or relied upon, for the purpose of (i) avoiding penalties under the Internal Revenue Code, or (ii) promoting, marketing or recommending to another party any transaction or matter addressed herein.
>
>E-mail is susceptible to data corruption, interception, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences
 thereof.
>
> 
>
>