Re: Inter provider communication

Yes in all of the provider types.  Each provider type defines its own 
specific interface.

In CMPI there is a specific set of function tables that allow 
"upcalls". Remember that in  CMPI the terminology is mi = provider mb 
= cimom so it is the CMPIBrokerFT. function table that encapsulates 
all of these upcalls (Both for requests to other providers and 
indication forward to the mb)

In C++ It is the CIMMONHandle that the provider gets as part of 
initialization that defines the class for the upcalls and there are 
upcalls for each of the client operations.

In general all of the client operations are supported except for some 
limitations in the associators, references, etc. where, for example 
CMPI only handles the instance requests, not the class requests 
(logical and correct).

It is important, in general to route requests through these 
interfaces (unless you are working in your own completely controlled 
provider module) since these interfaces provide services like 
security, etc. where as if you tried to directly route to another 
provider you would probably be bypassing some things.  This will 
become more important as we really implement the security profiles.

Karl

Thanks for your message at 01:16 PM 3/31/2013. Your message was:
>Hi,
>Is there support for inter-provider communication in Pegasus? Can 
>one provider send a WBEM request to another provider? I understand 
>that this can be achieved by creating a CIMClient and sending a 
>request to localhost, but is there a better way to communicate back 
>with the CIMOM from the provider to request this?
>Thanks
>Anuj

Karl Schopmeyer                   Inova Development Inc.
305 Spring Creek Village, Suite 475 -  Dallas TX, 75248 USA
EMAIL: [email protected]       FAX: 1-972-239-0326
Phone 1-972-814-5581
Skype: kschopmeyer         Skype Phone: (214) 556-5971